Hey there! Let's get this sorted out for you—since you're new to JMeter, I'll break this down step by step so it's easy to follow. BeanShell can be tricky for external process calls, so I'll start with the simplest, most reliable method first, then cover how to fix your BeanShell approach if you still want to use it.

This sampler is purpose-built for running external executables like batch files, so it avoids most of the pitfalls of BeanShell for this use case. Here's how to set it up:

• Open JMeter 3, create a new Test Plan, then right-click the Test Plan > Add > Threads (Users) > Thread Group. (You can leave the thread count at 1 for now since you're just testing.)
• Right-click your Thread Group > Add > Sampler > OS Process Sampler.
• Configure the sampler:
  • In the Command field, paste the full absolute path to your batch file (e.g., C:\my-app\run-my-jar.bat). Using absolute paths avoids any working directory confusion.
  • If your batch file needs command-line arguments (like passing parameters to your JAR), add each argument on a separate line in the Arguments section.
  • Optional: Set the Working Directory to the folder where your JAR and batch file live—this ensures any relative paths in the batch file work correctly.
• Add a listener to see results: Right-click the Thread Group > Add > Listener > View Results Tree. Run your test, and you'll see the batch file's output, exit code, and success status here.

If you still want to use BeanShell, the most common issues are incorrect file paths, unread process output (which can block the process), or missing working directory context. Try this code instead:

// Replace with your batch file's full path (use double backslashes for Java escape)
String batchPath = "C:\\my-app\\run-my-jar.bat";
// Replace with your JAR/batch working directory if needed
File workingDir = new File("C:\\my-app");

// Execute the batch file
Runtime runtime = Runtime.getRuntime();
Process process = runtime.exec(batchPath, null, workingDir);

// Critical: Read the process output to prevent it from hanging
BufferedReader inputReader = new BufferedReader(new InputStreamReader(process.getInputStream()));
BufferedReader errorReader = new BufferedReader(new InputStreamReader(process.getErrorStream()));

// Log output to JMeter's logs (check jmeter.log)
String line;
while ((line = inputReader.readLine()) != null) {
    log.info("Batch Output: " + line);
}
while ((line = errorReader.readLine()) != null) {
    log.warn("Batch Error: " + line);
}

// Wait for the process to finish and get exit code
int exitCode = process.waitFor();
log.info("Batch Exit Code: " + exitCode);

// Update the sampler result so you can see status in listeners
SampleResult.setResponseCode(String.valueOf(exitCode));
if (exitCode == 0) {
    SampleResult.setSuccessful(true);
    SampleResult.setResponseData("Batch executed successfully", "UTF-8");
} else {
    SampleResult.setSuccessful(false);
    SampleResult.setResponseData("Batch failed with exit code: " + exitCode, "UTF-8");
}

Key fixes from what you might have tried before:

• Uses absolute paths and explicit working directory to avoid path errors
• Reads both standard output and error streams (this is a big one—if you don't read these, the process can hang indefinitely)
• Sets the sampler's success status based on the batch file's exit code, so you can see pass/fail in JMeter's listeners

Before you run anything in JMeter:

• Double-check that your batch file works when you run it manually (double-click it or run it from Command Prompt). If it fails there, JMeter won't fix it!
• Make sure JMeter has permission to execute the batch file and access the JAR (avoid placing files in restricted folders like C:\Windows or Program Files without admin rights)
• JMeter 3 is compatible with Java 8—if you're using a newer Java version, you might run into issues, so stick with Java 8 if possible

内容的提问来源于stack exchange，提问作者kabisko