Sometimes JMeter stops unexpectedly with a fatal error

[J]

Hi All,

I don't know whether it's the JMeter issue or the AutoStop plugin but sometimes when I run tests in CLI mode, jmeter stops unexpectedly with a fatal error without printing a "...end of run" msg in the jmeter log.

Here's an excerpt from the jmeter log when the run finished properly:

Generate Summary Results +     32 in    14s =    2.4/s Avg:   101 Min:     6 Max:   397 Err:     0 (0.00%) Active: 0 Started: 30 Finished: 30
Generate Summary Results =   2463 in   346s =    7.1/s Avg:   232 Min:     5 Max:  2679 Err:     0 (0.00%)
Tidying up ...    @ Tue Oct 22 18:42:43 BST 2013 (1382463763814)
... end of run

and here's one when it failed to do so:

Generate Summary Results +    352 in    15s =   24.2/s Avg:    46 Min:    15 Max:   282 Err:     0 (0.00%) Active: 100 Started: 100 Finished: 0
Generate Summary Results =   2374 in   118s =   20.1/s Avg:    52 Min:    14 Max: 10115 Err:     2 (0.08%)
Command: StopTestNow received from /127.0.0.1
Fatal error, could not stop test, exitting

The problem with the latter one is the lack of "... end of run" entry, which https://github.com/oliverlloyd/jmeter-ec2 project is using to detect when JMeter stopped running the test.

I found in the JMeter src code where this error is printed: http://svn.apache.org/viewvc/jmeter/trunk/src/core/org/apache/jmeter/engine/StandardJMeterEngine.java?view=markup#l285

But still I'm not sure whether AutoStop plugin has something to do with it or not.

Cheers,

Janusz

[Andrey Pohilko]

Yes, JMeter sometimes have a problems with correct shutdown. 

I think the best way to solve this issue is to make change in jmeter-ec2 script. This script should have ability to detect any of JMeter stop situations, either successfull, or erroneous. I think you can send a pull request to Oliver Lloyd to implement this.

среда, 23 октября 2013 г., 15:32:36 UTC+4 пользователь J написал:

[J]

Cool, will do :)

Cheers Mate!

[gli...@gmail.com]

From time to time I was facing similar errors especially when running JMeter tests in distributed mode assuming huge load and immense traffic between JMeter server and remote engines. I worked it around by configuring JMeter to send data to server in lesser chunks and more frequently, lowering the load on each engine by increasing number of remote instances as it itsn't recommended to spawn more than 300 threads per host. Basic customizations allowed shutdown operations to complete gracefully. Make sure that you're following JMeter Best Practices guide as it may not be related to the plugin itself.