593912016-04-28 15:24:53 +0000In Distributed mode, the client exits abnormally at the end of test2016-04-28 20:20:16 +0000111UnclassifiedJMeterMain2.13AllAllRESOLVEDFIXEDP2normal---1supportissuessupport0oldest_to_newest1906240support2016-04-28 15:24:53 +0000We noticed the following issue :
Run : jmeter-server -l jmeter-server.log
Run : /jmeter -r -X -n -t /data/jmeter/re7-3.0.jmx -l /data/jmeter/re7/results-rc3-remote.csv
In 2.13, this has the impact of not calling:
println("... end of run");
checkForRemainingThreads();
In 3.0 this has the impact of not generating the Report if called with additional options:
> -e -o /data/jmeter/re7/report-rc3-2
Issue is due to the thread.interrupt being called on RMI Reaper Thread.
IN 3.0:
https://github.com/apache/jmeter/blob/trunk/src/core/org/apache/jmeter/JMeter.java#L1127
It appears that t.interrupt() on RMI Reaper thread:
https://github.com/apache/jmeter/blob/trunk/src/core/org/apache/jmeter/engine/ClientJMeterEngine.java#L1711906251support2016-04-28 15:31:06 +0000See this bug reported towards jmeter maven plugin:
https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues/37
""Test has ended" is no longer present in the log file when jmeter interrupts the thead.
...."1906262sebb2016-04-28 15:34:08 +0000Note: a workround is to generate the report once the run has finished, using a command of the form:
$ jmeter -g /data/jmeter/re7/results-rc3-remote.csv -o /data/jmeter/re7/report-rc3-21906383support2016-04-28 20:20:16 +0000Author: pmouawad
Date: Thu Apr 28 20:18:51 2016
New Revision: 1741507
URL: http://svn.apache.org/viewvc?rev=1741507&view=rev
Log:
Bug 59391 - In Distributed mode, the client exits abnormally at the end of test
Bugzilla Id: 59391
Modified:
jmeter/trunk/src/core/org/apache/jmeter/JMeter.java
jmeter/trunk/xdocs/changes.xml