Re: Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

We could open an issue with the custom sampler's author. But in the context of a test, I believe it is a bit extreme to "hang" because a thread did not exit: at least it should exit and fail the test plan cases affected by a sampler(s) not closing (their) threads, so that there is a result to inve

Re: Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

On 3 April 2014 09:43, Jean FX 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 > jmeter

Re: Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

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

Re: Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

On 2 April 2014 17:37, Jean FX 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

Re: Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

Hello, Since JMeter 2.10, there is a new property: - jmeterengine.force.system.exit Which you can set to true . This forces NON-GUI JVM to exit after test end. -- Regards Ubik Load Pack Team Follow us on Twitter Cordialement L

Should we not not have a feature to force the exit of JVM in case of "The JVM should have exitted but did not."

When the bellow happens in server mode, jmeter does not exit. Is this not a bug? [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)