https://bz.apache.org/bugzilla/show_bug.cgi?id=59391
Bug ID: 59391
Summary: In Distributed mode, the client exits abnormally at
the end of test
Product: JMeter
Version: 2.13
Hardware: Macintosh
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
We 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#L171
--
You are receiving this mail because:
You are the assignee for the bug.
