You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Jean FX <xo...@gmail.com> on 2014/04/02 18:37:00 UTC
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)
[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)
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."
Posted by Jean FX <xo...@gmail.com>.
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 investigate.
On Thu, Apr 3, 2014 at 2:54 PM, sebb <se...@gmail.com> wrote:
> On 3 April 2014 09:43, Jean FX <xo...@gmail.com> 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 <se...@gmail.com> wrote:
> >
> >> On 2 April 2014 17:37, Jean FX <xo...@gmail.com> 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: user-unsubscribe@jmeter.apache.org
> >> For additional commands, e-mail: user-help@jmeter.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
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."
Posted by sebb <se...@gmail.com>.
On 3 April 2014 09:43, Jean FX <xo...@gmail.com> 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 <se...@gmail.com> wrote:
>
>> On 2 April 2014 17:37, Jean FX <xo...@gmail.com> 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: user-unsubscribe@jmeter.apache.org
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
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."
Posted by Jean FX <xo...@gmail.com>.
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.
On Wed, Apr 2, 2014 at 11:40 PM, sebb <se...@gmail.com> wrote:
> On 2 April 2014 17:37, Jean FX <xo...@gmail.com> 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: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
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."
Posted by sebb <se...@gmail.com>.
On 2 April 2014 17:37, Jean FX <xo...@gmail.com> 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: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
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."
Posted by UBIK LOAD PACK Support <su...@ubikloadpack.com>.
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 <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>
On Wed, Apr 2, 2014 at 6:37 PM, Jean FX <xo...@gmail.com> wrote:
> 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)
> [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)
>
<http://twitter.com/ubikloadpack>