Hi, To reproduce (it is always reproducable): - Run locally a jmeter-server - Run a client (Debug this in your IDE ): ./jmeter -r -n -t <Any test plan having pauses> -l /data/jmeter/re7/results-rc3-remote.csv -e -o /data/jmeter/re7/report-rc3-2
Regards On Fri, Apr 29, 2016 at 2:06 PM, sebb <[email protected]> wrote: > I assume that the fix works, however I have not been able to reproduce > the original issue. > Maybe it needs a more complicated test. Has anyone else got a reproducer? > > However I wonder if this is the correct solution? > > The bug mentions TidyRMI, but I don't see how that is relevant. > The intention is that the TidyRMI method is be called after the test > is complete, in order to allow JMeter to exit cleanly. Also it only > interrupts the "RMI Reaper" thread, so it should not have an effect on > anything else. > > If it is somehow interfering with threads that are doing work, then > this ought to be fixed if possible. > > It also seems wrong to create a non-Daemon thread in a Daemon thread - > that seems very fragile. > > I suspect that is the real issue - since we expect the ListenToTest > thread to complete, it should not be a Daemon thread. > -- Regards Ubik Load Pack <http://ubikloadpack.com> Team Follow us on Twitter <http://twitter.com/ubikloadpack> Cordialement L'équipe Ubik Load Pack <http://ubikloadpack.com> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
