\n
I also tried to open the mirror-server.cmd to troubleshoot:
\n\nBy double clicking these exe file in the JMeter bin folder (I tried to click both but same error).\n
And suddenly my test is running almost 20k VUs now:\n
I also already restart my pc and try to run again with 500 VUs, but the number doesn't start with 500 VUs instead, it is starting with 5000 VUs!\n
Can advise what is the issue here? Is the root cause come from the second round which does not finished the test? Luckily I don't encounter any errors of Out of Memory at the moment. How to force stop all tests that currently running in the command? Please advise, thanks!
\n","author":{"@type":"Person","name":"emeraldgold07"},"upvoteCount":0,"answerCount":1,"acceptedAnswer":null}}Reputation: 303
I am running the test for API Performance testing for 2000 users in CLI Mode at first. Second round of test with 5000 VUs but the second round the test won't stop. I run for for interval time of 12 minutes but past 12 minutes the test still dont finish the thread by 5000 VUs.
So I want to shutdown the test running. This error occurs when I want to stop the test running (click shutdown.cmd)
I also tried to open the mirror-server.cmd to troubleshoot:
By double clicking these exe file in the JMeter bin folder (I tried to click both but same error).
And suddenly my test is running almost 20k VUs now:
I also already restart my pc and try to run again with 500 VUs, but the number doesn't start with 500 VUs instead, it is starting with 5000 VUs!
Can advise what is the issue here? Is the root cause come from the second round which does not finished the test? Luckily I don't encounter any errors of Out of Memory at the moment. How to force stop all tests that currently running in the command? Please advise, thanks!
Upvotes: 0
Views: 2960
Reputation: 168157
These are not .exe
files, they are Windows Batch scripts
I cannot reproduce your issue using the steps you provided:
You can try stopping your test by running this shutdown.cmd
from the "bin" folder of your JMeter installation from Windows Command Prompt
You can just press Control
+ C
in the shell window where your test is running to stop it
As the last resort you can always use taskkill command to terminate all Java processes
taskkill /f /im "java.exe"
Warning: it will terminate all Java process instances, not only JMeter
The number of active threads is in this column:
It's hard to say why your test is not ending without seeing your test configuration and jmeter.log file preferably with debug logging enabled for the Thread Group and Timer components you're using
Upvotes: 0