On 3 April 2014 09:43, Jean FX <[email protected]> wrote: > Thanks a lot for that setting! > > @Sebb, in my case I really do not care why the threads did not exit (I am > using a custom 3rd party sampler that clearly does not exit while waiting > for TCP sockets to close and jMeter does show this) so the new > jmeterengine.force.system.exit setting is perfect for me.
Perhaps raise a bug with the sampler supplier? > > On Wed, Apr 2, 2014 at 11:40 PM, sebb <[email protected]> wrote: > >> On 2 April 2014 17:37, Jean FX <[email protected]> wrote: >> > When the bellow happens in server mode, jmeter does not exit. Is this >> not a >> > bug? >> >> No, it's not a bug in JMeter; it's not generally good practice to exit >> an application untill all non-daemon threads have completed. >> >> It may be a bug in the test or perhaps in the JVM. >> >> Ideally you need to find out why some threads have failed to complete. >> >> See also the reply regarding the property jmeterengine.force.system.exit. >> This will cause JMeter to ignore the unfinished threads. >> >> > [jmeter] Starting the test @ Wed Apr 02 18:24:11 SAST 2014 >> (1396455851107) >> > [jmeter] Waiting for possible shutdown message on port 4445 >> > [jmeter] Tidying up ... @ Wed Apr 02 18:32:53 SAST 2014 >> > (1396456373022) >> > [jmeter] ... end of run >> > [jmeter] The JVM should have exitted but did not. >> > [jmeter] The following non-daemon threads are still running >> > (DestroyJavaVM is OK) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
