# 9.9 - Appvance - Jmeter Appvance - Jmeter — Knowledge Base articles. # Appvance - Jmeter (KB) ## Contents - [File Downloads from JMeter](/books/appvance-jmeter/page/file-downloads-from-jmeter) - [How to run Jmeter DB script in AIQ](/books/appvance-jmeter/page/how-to-run-jmeter-db-script-in-aiq) - [Jmeter - Java.lang.RuntimeException: Could not find the TestPlan class!](/books/appvance-jmeter/page/jmeter-javalangruntimeexception-could-not-find-the-testplan-class) - [Error Running](/books/appvance-jmeter/page/error-running) - [JMeter - Note able to see the transactions in the Reports or Test Controller.](/books/appvance-jmeter/page/jmeter-note-able-to-see-the-transactions-in-the-reports-or-test-controller) - [Jmeter - Steps Average duration calculation in Appvance IQ](/books/appvance-jmeter/page/jmeter-steps-average-duration-calculation-in-appvance-iq) - [Jmeter: Error while running MySQL DB script](/books/appvance-jmeter/page/jmeter-error-while-running-mysql-db-script) - [Running Jmeter Scripts in AIQ - Best Practices](/books/appvance-jmeter/page/running-jmeter-scripts-in-aiq-best-practices) - [Adding Plugins in a Jmeter Execution](/books/appvance-jmeter/page/adding-plugins-in-a-jmeter-execution) - [File Downloads from JMeter ](/books/appvance-jmeter/page/file-downloads-from-jmeter) - [How to run Jmeter DB script in AIQ ](/books/appvance-jmeter/page/how-to-run-jmeter-db-script-in-aiq) - [Jmeter: Error while running MySQL DB script ](/books/appvance-jmeter/page/jmeter-error-while-running-mysql-db-script) - [Jmeter - Java.lang.RuntimeException: Could not find the TestPlan class! Getting this error while running the scenario from AIQ. ](/books/appvance-jmeter/page/jmeter-javalangruntimeexception-could-not-find-the-testplan-class) - [JMeter - Note able to see the transactions in the Reports or Test Controller. ](/books/appvance-jmeter/page/jmeter-note-able-to-see-the-transactions-in-the-reports-or-test-controller) - [Jmeter - Steps Average duration calculation in Appvance IQ ](/books/appvance-jmeter/page/jmeter-steps-average-duration-calculation-in-appvance-iq) - [Running Jmeter Scripts in AIQ - Best Practices ](/books/appvance-jmeter/page/running-jmeter-scripts-in-aiq-best-practices)
--- Last updated: June 01, 2023 If you have any feedback on this topic, please contact us at
# Validate File Downloads in JMeter Tests # Validate File Downloads in JMeter Tests **Last reviewed:** September 21, 2026 Use this page when a JMeter-based AIQ test needs to request and validate downloadable files. Focus on response validation rather than browser download behavior. ## When to use this guidance - A JMeter scenario downloads files or reports from an application. - You need to validate content type, size, status code, or response body. - The test should avoid storing unnecessary files on load generators. ## Recommended approach 1. Confirm the download request works manually and capture the expected headers. 2. Configure the JMeter sampler to request the file endpoint directly. 3. Add assertions for HTTP status, content type, size, or checksum when practical. 4. Parameterize file IDs or URLs through AIQ data sources if multiple files are tested. 5. Clean up any saved artifacts and avoid writing large files during high-volume load tests. **Note:** For browser-driven downloads, use Scenario Editor download validation guidance instead of this JMeter-specific page. --- Last updated: September 21, 2026 If you have feedback on this topic, contact . # Run JMeter Database Scripts in AIQ # Run JMeter Database Scripts in AIQ **Last reviewed:** September 21, 2026 Use this article when AIQ executes a JMeter plan that includes database access. Keep credentials secure and validate database impact before running load. ## When to use this guidance - A JMeter test plan uses JDBC or database queries. - The test is executed or scheduled through AIQ. - You need to validate connectivity, drivers, credentials, and result handling. ## Recommended approach 1. Confirm the database endpoint and account are approved for test use. 2. Package the required JDBC driver and verify it is available to the JMeter runtime. 3. Store credentials through approved secret handling rather than hard-coding them in the test plan. 4. Run a small smoke execution in AIQ before scaling concurrency. 5. Monitor database load and clean up test data after execution. **Note:** Database load tests can affect shared environments. Coordinate with database owners before running high-volume scenarios. --- Last updated: September 21, 2026 If you have feedback on this topic, contact . # HTMLUnit Bundle Required When Running a Scenario # Issue An error occurs when running a scenario from AIQ because the required HTMLUnit bundle is not available. ## Solution Add the required **htmlunit** bundle to the scenario resources. 1. Navigate to **Scenario Builder** and open the scenario. 2. Open the **Resource Panel**. 3. Click **Add Bundle**. 4. Add the following bundle: - **Bundle:** `htmlunit` - **Version:** `2.15.2648` 5. Click **Save**. 6. Re-run the scenario. The scenario should run successfully after the required HTMLUnit bundle has been added. --- **Last updated:** August 19, 2026 If you have any feedback on this topic, please contact us at . # Understand JMeter Step Average Duration in AIQ # Understand JMeter Step Average Duration in AIQ JMeter step average duration summarizes the timing of completed steps or transactions captured during an AIQ execution. Use it as a trend indicator, not as the only measure of performance quality. ## How to interpret it - The average is affected by slow outliers, failed samples, and the selected result interval. - Compare averages only between runs with the same script, data, environment, and load model. - Use percentiles, error rate, and throughput with the average to understand performance behavior. ## Recommended workflow 1. Confirm the JMeter transactions are named clearly before execution. 2. Review failed samples before interpreting timing metrics. 3. Compare steady-state periods rather than ramp-up or ramp-down. 4. Document the run ID, load level, and environment when sharing results. **Last updated:** September 18, 2026 # Troubleshoot JMeter MySQL Script Errors in AIQ **Last reviewed:** September 29, 2026 Use this article when a JMeter script fails in AIQ while connecting to or querying a MySQL database. ## What changed in this article - Changed the title from a generic error phrase into a troubleshooting task for JMeter + MySQL. - Added specific checks for JDBC driver availability, connection string, credentials, network access, SQL permissions, and test data state. - Separated database connectivity failures from JMeter assertion or script logic failures. ## Validation workflow 1. Confirm the MySQL JDBC driver is available to the execution environment. 2. Validate the JDBC URL, user permissions, network route, and database state outside the full AIQ run. 3. Run a small JMeter query test in AIQ and compare the error output with the database logs. **Review note:** The page now helps isolate whether the failure is driver/configuration/network/database permission rather than just “JMeter failed.” --- Last updated: September 29, 2026 If you have feedback on this topic, contact . # Running JMeter Scripts in AIQ - Best Practices # Running JMeter Scripts in AIQ - Best Practices Use this guidance when running Apache JMeter scripts through AIQ. Keep scripts portable, parameterized, and observable so results can be compared across environments and test runs. ## Best practices - Keep JMeter scripts environment-neutral by using variables for hostnames, credentials, ports, and test data. - Validate the script locally or in a small AIQ run before scheduling high-volume execution. - Use realistic think time, ramp-up, and concurrency settings that match the test objective. - Externalize test data and avoid embedding secrets in JMX files. - Capture transaction naming consistently so AIQ reports remain readable. - Monitor Controller and Test Node resources during large JMeter runs. ## Validation workflow 1. Run a single-user smoke test and confirm expected transactions appear in AIQ results. 2. Increase load gradually while watching errors, response time, and node capacity. 3. Review logs for missing files, plugin dependencies, or variable-resolution failures. *Last updated: October 8, 2026* # Add JMeter Plugins for AIQ Executions **Last reviewed:** September 30, 2026 Use this article when an AIQ JMeter execution requires a supported JMeter plugin that is not included in the base runtime. ## What changed in this article - Corrected capitalization/grammar from “Jmeter” to “JMeter” and framed plugin use as a controlled dependency task. - Added compatibility checks for plugin version, JMeter version, Test Node availability, restart needs, and result parser impact. - Added a caution to avoid installing arbitrary plugins directly into shared execution environments without review. ## Validation workflow 1. Confirm the JMeter plugin is required and compatible with the AIQ-supported JMeter version. 2. Install or stage the plugin through the approved Test Node/runtime process, then restart only the required services. 3. Run a small JMeter execution and verify logs, transactions, and reports before using the plugin in larger runs. **Review note:** This page now focuses on safe plugin dependency management for AIQ JMeter execution. --- Last updated: September 30, 2026 If you have feedback on this topic, contact .