It might indicate that the machine you’re running JMeter at is overloaded.
- Don’t run load tests using GUI mode, GUI is designed for tests development and debugging only, when it comes to test execution make sure to run your test in command-line non-GUI mode
- Make sure you’re following JMeter Best Practices and recommendations from the 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure guide.
- Make sure JMeter has enough headroom to operate in terms of CPU, RAM, Network and Disk IO. If machine doesn’t have enough resources to simulate that many users as you defined your results will not be accurate as JMeter will not be able to send requests fast enough. You can monitor baseline underlying OS health metrics using i.e. PerfMon Plugin
Assuming all above you should be able to terminate your test gracefully using either
shutdown.cmd shell script or forcefully using
stoptest.cmd script. Both scripts are located under “bin” folder of your JMeter installation.
If after applying above hints you still experience problems you will have to consider going for Distributed Testing as it indicates that single machine cannot kick off that many threads (virtual users) as you require.