You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Daniel Kurtz <dk...@olenick.com> on 2007/01/22 18:10:57 UTC
Thread won't die issue
We find that invariably we end up with more or less a number of threads that don't go into an 'ending' status. Of course the test itself does not end in these circumstances, but will just hang out there forever. When we force a stop from the console, the end of jmeter.log ends up looking like:
...
2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-500 is done
2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending thread 499
2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread Group 1-271
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread won't die: Thread Group 1-271
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local)
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has ended
Suggestions as to what we should look at to resolve this?
Thanks.
Daniel Kurtz
Re: [Newbie] SV: Thread won't die issue
Posted by Alexander J Turner <gi...@cubicalland.com>.
Sebb,
I think there is a good chance that you are half write. I have
investigated the issue of running out of sockets on a windows server.
The machine can run out of sockets, but it does this in a controlled
way. However, I suspect that under very heavy concurrent load windows
fails to send socket closed messages properly. I have no real proof of
this (ie I have not traced the socket chatter) as - frankly - I don't
have a machine powerful enough to monitor that much traffic. However,
Windows not closing sockets properly fits all the hanging results I have
seen.
Cheers
AJ
On Fri, 2007-03-02 at 09:50 +0000, sebb wrote:
> Just realised that there is another possibility that might be
> affecting testing with lots of threads:
>
> The host might be running out of sockets or having problems releasing them.
>
> When the hang occurs, try starting a browser on the same host and see
> if you can connect to the server under test and/or some other server.
>
> S///
> On 02/03/07, Marlon Santos <ms...@exist.com> wrote:
> >
> > Ok thanks... I will be trying this and will be keeping you posted...
> >
> >
> >
> >
> > sebb-2 wrote:
> > >
> > > If it is JMeter, then we will either need a repeatable test-case to
> > > investigate further, or someone who is experiencing the problem may be
> > > able to gather some further data about the state of JMeter: e.g. are
> > > there any deadlocks?
> > >
> > > In answer to Marlon, I suggest you try:
> > > - removing all unnecessary Listeners. You should only need one.
> > > - running in non-GUI mode
> > >
> > > Both of these reduce the load on JMeter.
> > >
> > > If that does not solve the problem, then try using multiple JMeter
> > > instances. If you then still get hangs, it is unlikely to be JMeter
> > > that is at fault.
> > >
> > > S///
> > > On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> > >> Nino,
> > >>
> > >> This is an issue that has cropped up in the past. In my experiance,
> > >> JMeter (and I am not convinced it is JMeter's fault - it could be to do
> > >> with Java) hangs when there are a lot of threads. I have seen this when
> > >> I know it is not the web server that is hanging, because I was
> > >> load-testing TAG, a web server that has a radically different approach
> > >> to the likes of Apache and IIS, and for which I could monitor all the
> > >> internals. I have also seen this on Linux and Window XP.
> > >>
> > >> I think the real issue is that no software works well with very large
> > >> numbers of threads. If you really want to run vast numbers of
> > >> concurrent actions, you need a non-blocking approach. Note, Apache does
> > >> not uses non-blocking, but it does thread pooling, which results in it
> > >> actually not handling large numbers of concurrent activities, it just
> > >> lets the OS queue them.
> > >>
> > >> The only real way to destruction test a web server is to have multiple
> > >> machines hitting it at once, you cannot expect a single machine running
> > >> multiple virtual clients to do the job.
> > >>
>
> Unless the server does not handle multiple connections very well ...!
>
> > >> Best wishes
> > >>
> > >> AJ
> > >>
> > >> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> > >> > This is pretty interesting..!
> > >> >
> > >> > We also experience something like that. My best guess rigth now are
> > >> that it's because the http server arent able to handle all those requests
> > >> at the same time, and some of them does not get a response, hence the
> > >> hanging thread.
> > >> >
> > >> > What happens in your scenario if you abort the test (ctrl+.) and run it
> > >> again. Is it the exact same number of threads that are hanging?
> > >> >
> > >> > regards Nino
> > >> >
> > >> > ________________________________
> > >> >
> > >> > Fra: Marlon Santos [mailto:msantos@exist.com]
> > >> > Sendt: to 01-03-2007 02:30
> > >> > Til: jmeter-user@jakarta.apache.org
> > >> > Emne: Re: [Newbie] Thread won't die issue
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Hi,
> > >> >
> > >> > We are also experiencing the same thing. Actually we are in an
> > >> environment
> > >> > where we need to load test a website but when I was running the test on
> > >> > small number of virtual users it works fine. But later on, when we
> > >> increased
> > >> > the number of virtual users at some point in time the threads suddenly
> > >> > stopped responding, or may I say the threads hang. We are in a tight
> > >> > schedule so the faster this is resolved, the better it will be
> > >> > appreciated...
> > >> >
> > >> > Regards,
> > >> > Marlon
> > >> > --
> > >> > View this message in context:
> > >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> > >> > Sent from the JMeter - User mailing list archive at Nabble.com.
> > >> >
> > >> >
> > >> > ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >> --
> > >>
> > >> ==========================================
> > >> Hard Core How-To's, Coding Techniques ETC.
> > >> --- http://nerds-central.blogspot.com! ---
> > >> Nerds Central welcomes nerds :-)
> > >> ==========================================
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> > >
> >
> > --
> > View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
--
==========================================
Hard Core How-To's, Coding Techniques ETC.
--- http://nerds-central.blogspot.com! ---
Nerds Central welcomes nerds :-)
==========================================
Re: [Newbie] SV: Thread won't die issue
Posted by sebb <se...@gmail.com>.
On 06/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> Marlon,
>
> This is really important to get clear. You cannot load test one machine
> with one machine unless there is a large difference is performance
> between the server (small) and client (large). This is especially true
> of JMeter, which is not tuned for performance. A Apache linux server or
> Windows IIS server will totally and utterly outperform JMeter without
> breaking out a sweat.
That depends somewhat on how well the application is written - and
what it is doing.
JMeter running a simple test plan can generate quite a substantial
load; if the server has to do a lot of work for each request it may
well be possible to overload the server.
However, I agree that the machine running JMeter should not be running
at or near its limit, otherwise the test results may be somewhat
variable. Likewise the network connection from the test machine needs
to be able to cope with the load.
> Further, if it is possible for one client
> machine to load your server significantly, you have an issue!
Depends on what the server is designed to do ...
And may depend on the test plan. e.g. if the server provides different
services, some of which are rarely needed but which are very resource
intensive, then it may well be possible for a few client threads to
cause a problem for the server. But that does not necessarily mean the
server is faulty.
> Please have this in mind when you are designing your test cases.
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: [Newbie] SV: Thread won't die issue
Posted by Alexander J Turner <gi...@cubicalland.com>.
Marlon,
This is really important to get clear. You cannot load test one machine
with one machine unless there is a large difference is performance
between the server (small) and client (large). This is especially true
of JMeter, which is not tuned for performance. A Apache linux server or
Windows IIS server will totally and utterly outperform JMeter without
breaking out a sweat. Further, if it is possible for one client
machine to load your server significantly, you have an issue!
Please have this in mind when you are designing your test cases.
Best wishes
AJ
On Sun, 2007-03-04 at 17:47 -0800, Marlon Santos wrote:
> Hi,
>
> the problem still occurs.. i tried doing everything you said in the previous
> previous post but to no avail. May I ask, is there a recommended or
> preferred amount of virtual users and/or threads in running a test plan in
> jmeter? because we are in dire need of large volumes of user simulation. And
> about the multiple instances of JMeter that you suggested, is it alright if
> it is in the same machine or it should be on different machines? If ever it
> is alright on the SAME machine, will there be performance problems that may
> affect the results?
>
> Regards,
> Marlon
>
>
>
> sebb-2 wrote:
> >
> > Just realised that there is another possibility that might be
> > affecting testing with lots of threads:
> >
> > The host might be running out of sockets or having problems releasing
> > them.
> >
> > When the hang occurs, try starting a browser on the same host and see
> > if you can connect to the server under test and/or some other server.
> >
> > S///
> > On 02/03/07, Marlon Santos <ms...@exist.com> wrote:
> >>
> >> Ok thanks... I will be trying this and will be keeping you posted...
> >>
> >>
> >>
> >>
> >> sebb-2 wrote:
> >> >
> >> > If it is JMeter, then we will either need a repeatable test-case to
> >> > investigate further, or someone who is experiencing the problem may be
> >> > able to gather some further data about the state of JMeter: e.g. are
> >> > there any deadlocks?
> >> >
> >> > In answer to Marlon, I suggest you try:
> >> > - removing all unnecessary Listeners. You should only need one.
> >> > - running in non-GUI mode
> >> >
> >> > Both of these reduce the load on JMeter.
> >> >
> >> > If that does not solve the problem, then try using multiple JMeter
> >> > instances. If you then still get hangs, it is unlikely to be JMeter
> >> > that is at fault.
> >> >
> >> > S///
> >> > On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> >> >> Nino,
> >> >>
> >> >> This is an issue that has cropped up in the past. In my experiance,
> >> >> JMeter (and I am not convinced it is JMeter's fault - it could be to
> >> do
> >> >> with Java) hangs when there are a lot of threads. I have seen this
> >> when
> >> >> I know it is not the web server that is hanging, because I was
> >> >> load-testing TAG, a web server that has a radically different approach
> >> >> to the likes of Apache and IIS, and for which I could monitor all the
> >> >> internals. I have also seen this on Linux and Window XP.
> >> >>
> >> >> I think the real issue is that no software works well with very large
> >> >> numbers of threads. If you really want to run vast numbers of
> >> >> concurrent actions, you need a non-blocking approach. Note, Apache
> >> does
> >> >> not uses non-blocking, but it does thread pooling, which results in
> >> it
> >> >> actually not handling large numbers of concurrent activities, it just
> >> >> lets the OS queue them.
> >> >>
> >> >> The only real way to destruction test a web server is to have multiple
> >> >> machines hitting it at once, you cannot expect a single machine
> >> running
> >> >> multiple virtual clients to do the job.
> >> >>
> >
> > Unless the server does not handle multiple connections very well ...!
> >
> >> >> Best wishes
> >> >>
> >> >> AJ
> >> >>
> >> >> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> >> >> > This is pretty interesting..!
> >> >> >
> >> >> > We also experience something like that. My best guess rigth now are
> >> >> that it's because the http server arent able to handle all those
> >> requests
> >> >> at the same time, and some of them does not get a response, hence the
> >> >> hanging thread.
> >> >> >
> >> >> > What happens in your scenario if you abort the test (ctrl+.) and run
> >> it
> >> >> again. Is it the exact same number of threads that are hanging?
> >> >> >
> >> >> > regards Nino
> >> >> >
> >> >> > ________________________________
> >> >> >
> >> >> > Fra: Marlon Santos [mailto:msantos@exist.com]
> >> >> > Sendt: to 01-03-2007 02:30
> >> >> > Til: jmeter-user@jakarta.apache.org
> >> >> > Emne: Re: [Newbie] Thread won't die issue
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > Hi,
> >> >> >
> >> >> > We are also experiencing the same thing. Actually we are in an
> >> >> environment
> >> >> > where we need to load test a website but when I was running the test
> >> on
> >> >> > small number of virtual users it works fine. But later on, when we
> >> >> increased
> >> >> > the number of virtual users at some point in time the threads
> >> suddenly
> >> >> > stopped responding, or may I say the threads hang. We are in a tight
> >> >> > schedule so the faster this is resolved, the better it will be
> >> >> > appreciated...
> >> >> >
> >> >> > Regards,
> >> >> > Marlon
> >> >> > --
> >> >> > View this message in context:
> >> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> >> >> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >> >> >
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >> --
> >> >>
> >> >> ==========================================
> >> >> Hard Core How-To's, Coding Techniques ETC.
> >> >> --- http://nerds-central.blogspot.com! ---
> >> >> Nerds Central welcomes nerds :-)
> >> >> ==========================================
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
> >> Sent from the JMeter - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
>
--
==========================================
Hard Core How-To's, Coding Techniques ETC.
--- http://nerds-central.blogspot.com! ---
Nerds Central welcomes nerds :-)
==========================================
Re: [Newbie] SV: Thread won't die issue
Posted by sebb <se...@gmail.com>.
Did you try running a browser from the same machine when the problem occurred?
This should help show if the host is running out of ports.
As to how many users can be supported - well the answer is really how
many work OK - and that depends on the test plan and lots of other
factors.
Running separate instances of JMeter on the same host may or may not
help, depending on what the problem is: e.g. if the host is running
out of sockets, it probably won't help.
Certainly worth trying though. If it does work, then that suggests a
problem with JMeter and/or the JVM.
If you define the thread count and ramp-up using properties - e.g.
${__P(threads)} - you can pass this to the test plan as -Jthreads=123.
This makes it easy to test various scenarios.
S.
On 05/03/07, Marlon Santos <ms...@exist.com> wrote:
>
> Hi,
>
> the problem still occurs.. i tried doing everything you said in the previous
> previous post but to no avail. May I ask, is there a recommended or
> preferred amount of virtual users and/or threads in running a test plan in
> jmeter? because we are in dire need of large volumes of user simulation. And
> about the multiple instances of JMeter that you suggested, is it alright if
> it is in the same machine or it should be on different machines? If ever it
> is alright on the SAME machine, will there be performance problems that may
> affect the results?
>
> Regards,
> Marlon
>
>
>
> sebb-2 wrote:
> >
> > Just realised that there is another possibility that might be
> > affecting testing with lots of threads:
> >
> > The host might be running out of sockets or having problems releasing
> > them.
> >
> > When the hang occurs, try starting a browser on the same host and see
> > if you can connect to the server under test and/or some other server.
> >
> > S///
> > On 02/03/07, Marlon Santos <ms...@exist.com> wrote:
> >>
> >> Ok thanks... I will be trying this and will be keeping you posted...
> >>
> >>
> >>
> >>
> >> sebb-2 wrote:
> >> >
> >> > If it is JMeter, then we will either need a repeatable test-case to
> >> > investigate further, or someone who is experiencing the problem may be
> >> > able to gather some further data about the state of JMeter: e.g. are
> >> > there any deadlocks?
> >> >
> >> > In answer to Marlon, I suggest you try:
> >> > - removing all unnecessary Listeners. You should only need one.
> >> > - running in non-GUI mode
> >> >
> >> > Both of these reduce the load on JMeter.
> >> >
> >> > If that does not solve the problem, then try using multiple JMeter
> >> > instances. If you then still get hangs, it is unlikely to be JMeter
> >> > that is at fault.
> >> >
> >> > S///
> >> > On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> >> >> Nino,
> >> >>
> >> >> This is an issue that has cropped up in the past. In my experiance,
> >> >> JMeter (and I am not convinced it is JMeter's fault - it could be to
> >> do
> >> >> with Java) hangs when there are a lot of threads. I have seen this
> >> when
> >> >> I know it is not the web server that is hanging, because I was
> >> >> load-testing TAG, a web server that has a radically different approach
> >> >> to the likes of Apache and IIS, and for which I could monitor all the
> >> >> internals. I have also seen this on Linux and Window XP.
> >> >>
> >> >> I think the real issue is that no software works well with very large
> >> >> numbers of threads. If you really want to run vast numbers of
> >> >> concurrent actions, you need a non-blocking approach. Note, Apache
> >> does
> >> >> not uses non-blocking, but it does thread pooling, which results in
> >> it
> >> >> actually not handling large numbers of concurrent activities, it just
> >> >> lets the OS queue them.
> >> >>
> >> >> The only real way to destruction test a web server is to have multiple
> >> >> machines hitting it at once, you cannot expect a single machine
> >> running
> >> >> multiple virtual clients to do the job.
> >> >>
> >
> > Unless the server does not handle multiple connections very well ...!
> >
> >> >> Best wishes
> >> >>
> >> >> AJ
> >> >>
> >> >> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> >> >> > This is pretty interesting..!
> >> >> >
> >> >> > We also experience something like that. My best guess rigth now are
> >> >> that it's because the http server arent able to handle all those
> >> requests
> >> >> at the same time, and some of them does not get a response, hence the
> >> >> hanging thread.
> >> >> >
> >> >> > What happens in your scenario if you abort the test (ctrl+.) and run
> >> it
> >> >> again. Is it the exact same number of threads that are hanging?
> >> >> >
> >> >> > regards Nino
> >> >> >
> >> >> > ________________________________
> >> >> >
> >> >> > Fra: Marlon Santos [mailto:msantos@exist.com]
> >> >> > Sendt: to 01-03-2007 02:30
> >> >> > Til: jmeter-user@jakarta.apache.org
> >> >> > Emne: Re: [Newbie] Thread won't die issue
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > Hi,
> >> >> >
> >> >> > We are also experiencing the same thing. Actually we are in an
> >> >> environment
> >> >> > where we need to load test a website but when I was running the test
> >> on
> >> >> > small number of virtual users it works fine. But later on, when we
> >> >> increased
> >> >> > the number of virtual users at some point in time the threads
> >> suddenly
> >> >> > stopped responding, or may I say the threads hang. We are in a tight
> >> >> > schedule so the faster this is resolved, the better it will be
> >> >> > appreciated...
> >> >> >
> >> >> > Regards,
> >> >> > Marlon
> >> >> > --
> >> >> > View this message in context:
> >> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> >> >> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >> >> >
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >> --
> >> >>
> >> >> ==========================================
> >> >> Hard Core How-To's, Coding Techniques ETC.
> >> >> --- http://nerds-central.blogspot.com! ---
> >> >> Nerds Central welcomes nerds :-)
> >> >> ==========================================
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
> >> Sent from the JMeter - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9303389
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: [Newbie] SV: Thread won't die issue
Posted by Marlon Santos <ms...@exist.com>.
Hi,
the problem still occurs.. i tried doing everything you said in the previous
previous post but to no avail. May I ask, is there a recommended or
preferred amount of virtual users and/or threads in running a test plan in
jmeter? because we are in dire need of large volumes of user simulation. And
about the multiple instances of JMeter that you suggested, is it alright if
it is in the same machine or it should be on different machines? If ever it
is alright on the SAME machine, will there be performance problems that may
affect the results?
Regards,
Marlon
sebb-2 wrote:
>
> Just realised that there is another possibility that might be
> affecting testing with lots of threads:
>
> The host might be running out of sockets or having problems releasing
> them.
>
> When the hang occurs, try starting a browser on the same host and see
> if you can connect to the server under test and/or some other server.
>
> S///
> On 02/03/07, Marlon Santos <ms...@exist.com> wrote:
>>
>> Ok thanks... I will be trying this and will be keeping you posted...
>>
>>
>>
>>
>> sebb-2 wrote:
>> >
>> > If it is JMeter, then we will either need a repeatable test-case to
>> > investigate further, or someone who is experiencing the problem may be
>> > able to gather some further data about the state of JMeter: e.g. are
>> > there any deadlocks?
>> >
>> > In answer to Marlon, I suggest you try:
>> > - removing all unnecessary Listeners. You should only need one.
>> > - running in non-GUI mode
>> >
>> > Both of these reduce the load on JMeter.
>> >
>> > If that does not solve the problem, then try using multiple JMeter
>> > instances. If you then still get hangs, it is unlikely to be JMeter
>> > that is at fault.
>> >
>> > S///
>> > On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
>> >> Nino,
>> >>
>> >> This is an issue that has cropped up in the past. In my experiance,
>> >> JMeter (and I am not convinced it is JMeter's fault - it could be to
>> do
>> >> with Java) hangs when there are a lot of threads. I have seen this
>> when
>> >> I know it is not the web server that is hanging, because I was
>> >> load-testing TAG, a web server that has a radically different approach
>> >> to the likes of Apache and IIS, and for which I could monitor all the
>> >> internals. I have also seen this on Linux and Window XP.
>> >>
>> >> I think the real issue is that no software works well with very large
>> >> numbers of threads. If you really want to run vast numbers of
>> >> concurrent actions, you need a non-blocking approach. Note, Apache
>> does
>> >> not uses non-blocking, but it does thread pooling, which results in
>> it
>> >> actually not handling large numbers of concurrent activities, it just
>> >> lets the OS queue them.
>> >>
>> >> The only real way to destruction test a web server is to have multiple
>> >> machines hitting it at once, you cannot expect a single machine
>> running
>> >> multiple virtual clients to do the job.
>> >>
>
> Unless the server does not handle multiple connections very well ...!
>
>> >> Best wishes
>> >>
>> >> AJ
>> >>
>> >> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
>> >> > This is pretty interesting..!
>> >> >
>> >> > We also experience something like that. My best guess rigth now are
>> >> that it's because the http server arent able to handle all those
>> requests
>> >> at the same time, and some of them does not get a response, hence the
>> >> hanging thread.
>> >> >
>> >> > What happens in your scenario if you abort the test (ctrl+.) and run
>> it
>> >> again. Is it the exact same number of threads that are hanging?
>> >> >
>> >> > regards Nino
>> >> >
>> >> > ________________________________
>> >> >
>> >> > Fra: Marlon Santos [mailto:msantos@exist.com]
>> >> > Sendt: to 01-03-2007 02:30
>> >> > Til: jmeter-user@jakarta.apache.org
>> >> > Emne: Re: [Newbie] Thread won't die issue
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Hi,
>> >> >
>> >> > We are also experiencing the same thing. Actually we are in an
>> >> environment
>> >> > where we need to load test a website but when I was running the test
>> on
>> >> > small number of virtual users it works fine. But later on, when we
>> >> increased
>> >> > the number of virtual users at some point in time the threads
>> suddenly
>> >> > stopped responding, or may I say the threads hang. We are in a tight
>> >> > schedule so the faster this is resolved, the better it will be
>> >> > appreciated...
>> >> >
>> >> > Regards,
>> >> > Marlon
>> >> > --
>> >> > View this message in context:
>> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
>> >> > Sent from the JMeter - User mailing list archive at Nabble.com.
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >> --
>> >>
>> >> ==========================================
>> >> Hard Core How-To's, Coding Techniques ETC.
>> >> --- http://nerds-central.blogspot.com! ---
>> >> Nerds Central welcomes nerds :-)
>> >> ==========================================
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9303389
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: [Newbie] SV: Thread won't die issue
Posted by sebb <se...@gmail.com>.
Just realised that there is another possibility that might be
affecting testing with lots of threads:
The host might be running out of sockets or having problems releasing them.
When the hang occurs, try starting a browser on the same host and see
if you can connect to the server under test and/or some other server.
S///
On 02/03/07, Marlon Santos <ms...@exist.com> wrote:
>
> Ok thanks... I will be trying this and will be keeping you posted...
>
>
>
>
> sebb-2 wrote:
> >
> > If it is JMeter, then we will either need a repeatable test-case to
> > investigate further, or someone who is experiencing the problem may be
> > able to gather some further data about the state of JMeter: e.g. are
> > there any deadlocks?
> >
> > In answer to Marlon, I suggest you try:
> > - removing all unnecessary Listeners. You should only need one.
> > - running in non-GUI mode
> >
> > Both of these reduce the load on JMeter.
> >
> > If that does not solve the problem, then try using multiple JMeter
> > instances. If you then still get hangs, it is unlikely to be JMeter
> > that is at fault.
> >
> > S///
> > On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> >> Nino,
> >>
> >> This is an issue that has cropped up in the past. In my experiance,
> >> JMeter (and I am not convinced it is JMeter's fault - it could be to do
> >> with Java) hangs when there are a lot of threads. I have seen this when
> >> I know it is not the web server that is hanging, because I was
> >> load-testing TAG, a web server that has a radically different approach
> >> to the likes of Apache and IIS, and for which I could monitor all the
> >> internals. I have also seen this on Linux and Window XP.
> >>
> >> I think the real issue is that no software works well with very large
> >> numbers of threads. If you really want to run vast numbers of
> >> concurrent actions, you need a non-blocking approach. Note, Apache does
> >> not uses non-blocking, but it does thread pooling, which results in it
> >> actually not handling large numbers of concurrent activities, it just
> >> lets the OS queue them.
> >>
> >> The only real way to destruction test a web server is to have multiple
> >> machines hitting it at once, you cannot expect a single machine running
> >> multiple virtual clients to do the job.
> >>
Unless the server does not handle multiple connections very well ...!
> >> Best wishes
> >>
> >> AJ
> >>
> >> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> >> > This is pretty interesting..!
> >> >
> >> > We also experience something like that. My best guess rigth now are
> >> that it's because the http server arent able to handle all those requests
> >> at the same time, and some of them does not get a response, hence the
> >> hanging thread.
> >> >
> >> > What happens in your scenario if you abort the test (ctrl+.) and run it
> >> again. Is it the exact same number of threads that are hanging?
> >> >
> >> > regards Nino
> >> >
> >> > ________________________________
> >> >
> >> > Fra: Marlon Santos [mailto:msantos@exist.com]
> >> > Sendt: to 01-03-2007 02:30
> >> > Til: jmeter-user@jakarta.apache.org
> >> > Emne: Re: [Newbie] Thread won't die issue
> >> >
> >> >
> >> >
> >> >
> >> > Hi,
> >> >
> >> > We are also experiencing the same thing. Actually we are in an
> >> environment
> >> > where we need to load test a website but when I was running the test on
> >> > small number of virtual users it works fine. But later on, when we
> >> increased
> >> > the number of virtual users at some point in time the threads suddenly
> >> > stopped responding, or may I say the threads hang. We are in a tight
> >> > schedule so the faster this is resolved, the better it will be
> >> > appreciated...
> >> >
> >> > Regards,
> >> > Marlon
> >> > --
> >> > View this message in context:
> >> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> >> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> --
> >>
> >> ==========================================
> >> Hard Core How-To's, Coding Techniques ETC.
> >> --- http://nerds-central.blogspot.com! ---
> >> Nerds Central welcomes nerds :-)
> >> ==========================================
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: [Newbie] SV: Thread won't die issue
Posted by Marlon Santos <ms...@exist.com>.
Ok thanks... I will be trying this and will be keeping you posted...
sebb-2 wrote:
>
> If it is JMeter, then we will either need a repeatable test-case to
> investigate further, or someone who is experiencing the problem may be
> able to gather some further data about the state of JMeter: e.g. are
> there any deadlocks?
>
> In answer to Marlon, I suggest you try:
> - removing all unnecessary Listeners. You should only need one.
> - running in non-GUI mode
>
> Both of these reduce the load on JMeter.
>
> If that does not solve the problem, then try using multiple JMeter
> instances. If you then still get hangs, it is unlikely to be JMeter
> that is at fault.
>
> S///
> On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
>> Nino,
>>
>> This is an issue that has cropped up in the past. In my experiance,
>> JMeter (and I am not convinced it is JMeter's fault - it could be to do
>> with Java) hangs when there are a lot of threads. I have seen this when
>> I know it is not the web server that is hanging, because I was
>> load-testing TAG, a web server that has a radically different approach
>> to the likes of Apache and IIS, and for which I could monitor all the
>> internals. I have also seen this on Linux and Window XP.
>>
>> I think the real issue is that no software works well with very large
>> numbers of threads. If you really want to run vast numbers of
>> concurrent actions, you need a non-blocking approach. Note, Apache does
>> not uses non-blocking, but it does thread pooling, which results in it
>> actually not handling large numbers of concurrent activities, it just
>> lets the OS queue them.
>>
>> The only real way to destruction test a web server is to have multiple
>> machines hitting it at once, you cannot expect a single machine running
>> multiple virtual clients to do the job.
>>
>> Best wishes
>>
>> AJ
>>
>> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
>> > This is pretty interesting..!
>> >
>> > We also experience something like that. My best guess rigth now are
>> that it's because the http server arent able to handle all those requests
>> at the same time, and some of them does not get a response, hence the
>> hanging thread.
>> >
>> > What happens in your scenario if you abort the test (ctrl+.) and run it
>> again. Is it the exact same number of threads that are hanging?
>> >
>> > regards Nino
>> >
>> > ________________________________
>> >
>> > Fra: Marlon Santos [mailto:msantos@exist.com]
>> > Sendt: to 01-03-2007 02:30
>> > Til: jmeter-user@jakarta.apache.org
>> > Emne: Re: [Newbie] Thread won't die issue
>> >
>> >
>> >
>> >
>> > Hi,
>> >
>> > We are also experiencing the same thing. Actually we are in an
>> environment
>> > where we need to load test a website but when I was running the test on
>> > small number of virtual users it works fine. But later on, when we
>> increased
>> > the number of virtual users at some point in time the threads suddenly
>> > stopped responding, or may I say the threads hang. We are in a tight
>> > schedule so the faster this is resolved, the better it will be
>> > appreciated...
>> >
>> > Regards,
>> > Marlon
>> > --
>> > View this message in context:
>> http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
>> > Sent from the JMeter - User mailing list archive at Nabble.com.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> --
>>
>> ==========================================
>> Hard Core How-To's, Coding Techniques ETC.
>> --- http://nerds-central.blogspot.com! ---
>> Nerds Central welcomes nerds :-)
>> ==========================================
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9263341
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: SV: [Newbie] Thread won't die issue
Posted by sebb <se...@gmail.com>.
If it is JMeter, then we will either need a repeatable test-case to
investigate further, or someone who is experiencing the problem may be
able to gather some further data about the state of JMeter: e.g. are
there any deadlocks?
In answer to Marlon, I suggest you try:
- removing all unnecessary Listeners. You should only need one.
- running in non-GUI mode
Both of these reduce the load on JMeter.
If that does not solve the problem, then try using multiple JMeter
instances. If you then still get hangs, it is unlikely to be JMeter
that is at fault.
S///
On 01/03/07, Alexander J Turner <gi...@cubicalland.com> wrote:
> Nino,
>
> This is an issue that has cropped up in the past. In my experiance,
> JMeter (and I am not convinced it is JMeter's fault - it could be to do
> with Java) hangs when there are a lot of threads. I have seen this when
> I know it is not the web server that is hanging, because I was
> load-testing TAG, a web server that has a radically different approach
> to the likes of Apache and IIS, and for which I could monitor all the
> internals. I have also seen this on Linux and Window XP.
>
> I think the real issue is that no software works well with very large
> numbers of threads. If you really want to run vast numbers of
> concurrent actions, you need a non-blocking approach. Note, Apache does
> not uses non-blocking, but it does thread pooling, which results in it
> actually not handling large numbers of concurrent activities, it just
> lets the OS queue them.
>
> The only real way to destruction test a web server is to have multiple
> machines hitting it at once, you cannot expect a single machine running
> multiple virtual clients to do the job.
>
> Best wishes
>
> AJ
>
> On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> > This is pretty interesting..!
> >
> > We also experience something like that. My best guess rigth now are that it's because the http server arent able to handle all those requests at the same time, and some of them does not get a response, hence the hanging thread.
> >
> > What happens in your scenario if you abort the test (ctrl+.) and run it again. Is it the exact same number of threads that are hanging?
> >
> > regards Nino
> >
> > ________________________________
> >
> > Fra: Marlon Santos [mailto:msantos@exist.com]
> > Sendt: to 01-03-2007 02:30
> > Til: jmeter-user@jakarta.apache.org
> > Emne: Re: [Newbie] Thread won't die issue
> >
> >
> >
> >
> > Hi,
> >
> > We are also experiencing the same thing. Actually we are in an environment
> > where we need to load test a website but when I was running the test on
> > small number of virtual users it works fine. But later on, when we increased
> > the number of virtual users at some point in time the threads suddenly
> > stopped responding, or may I say the threads hang. We are in a tight
> > schedule so the faster this is resolved, the better it will be
> > appreciated...
> >
> > Regards,
> > Marlon
> > --
> > View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> --
>
> ==========================================
> Hard Core How-To's, Coding Techniques ETC.
> --- http://nerds-central.blogspot.com! ---
> Nerds Central welcomes nerds :-)
> ==========================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: SV: [Newbie] Thread won't die issue
Posted by Alexander J Turner <gi...@cubicalland.com>.
Nino,
This is an issue that has cropped up in the past. In my experiance,
JMeter (and I am not convinced it is JMeter's fault - it could be to do
with Java) hangs when there are a lot of threads. I have seen this when
I know it is not the web server that is hanging, because I was
load-testing TAG, a web server that has a radically different approach
to the likes of Apache and IIS, and for which I could monitor all the
internals. I have also seen this on Linux and Window XP.
I think the real issue is that no software works well with very large
numbers of threads. If you really want to run vast numbers of
concurrent actions, you need a non-blocking approach. Note, Apache does
not uses non-blocking, but it does thread pooling, which results in it
actually not handling large numbers of concurrent activities, it just
lets the OS queue them.
The only real way to destruction test a web server is to have multiple
machines hitting it at once, you cannot expect a single machine running
multiple virtual clients to do the job.
Best wishes
AJ
On Thu, 2007-03-01 at 09:42 +0100, Nino Wael wrote:
> This is pretty interesting..!
>
> We also experience something like that. My best guess rigth now are that it's because the http server arent able to handle all those requests at the same time, and some of them does not get a response, hence the hanging thread.
>
> What happens in your scenario if you abort the test (ctrl+.) and run it again. Is it the exact same number of threads that are hanging?
>
> regards Nino
>
> ________________________________
>
> Fra: Marlon Santos [mailto:msantos@exist.com]
> Sendt: to 01-03-2007 02:30
> Til: jmeter-user@jakarta.apache.org
> Emne: Re: [Newbie] Thread won't die issue
>
>
>
>
> Hi,
>
> We are also experiencing the same thing. Actually we are in an environment
> where we need to load test a website but when I was running the test on
> small number of virtual users it works fine. But later on, when we increased
> the number of virtual users at some point in time the threads suddenly
> stopped responding, or may I say the threads hang. We are in a tight
> schedule so the faster this is resolved, the better it will be
> appreciated...
>
> Regards,
> Marlon
> --
> View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
==========================================
Hard Core How-To's, Coding Techniques ETC.
--- http://nerds-central.blogspot.com! ---
Nerds Central welcomes nerds :-)
==========================================
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
SV: [Newbie] Thread won't die issue
Posted by Nino Wael <Ni...@sdk.sas.com>.
This is pretty interesting..!
We also experience something like that. My best guess rigth now are that it's because the http server arent able to handle all those requests at the same time, and some of them does not get a response, hence the hanging thread.
What happens in your scenario if you abort the test (ctrl+.) and run it again. Is it the exact same number of threads that are hanging?
regards Nino
________________________________
Fra: Marlon Santos [mailto:msantos@exist.com]
Sendt: to 01-03-2007 02:30
Til: jmeter-user@jakarta.apache.org
Emne: Re: [Newbie] Thread won't die issue
Hi,
We are also experiencing the same thing. Actually we are in an environment
where we need to load test a website but when I was running the test on
small number of virtual users it works fine. But later on, when we increased
the number of virtual users at some point in time the threads suddenly
stopped responding, or may I say the threads hang. We are in a tight
schedule so the faster this is resolved, the better it will be
appreciated...
Regards,
Marlon
--
View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: [Newbie] Thread won't die issue
Posted by Marlon Santos <ms...@exist.com>.
Hi,
We are also experiencing the same thing. Actually we are in an environment
where we need to load test a website but when I was running the test on
small number of virtual users it works fine. But later on, when we increased
the number of virtual users at some point in time the threads suddenly
stopped responding, or may I say the threads hang. We are in a tight
schedule so the faster this is resolved, the better it will be
appreciated...
Regards,
Marlon
--
View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a9241968
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Thread won't die issue
Posted by Al_Sweetman <al...@gmail.com>.
AFAIK, Green threads have been replaced/superseded by native OS threads since
version 1.2... And the native OS threading now used has solved the
reliability (well, some anyway) issues.
Now: We're experiencing the same problem here - our platform is as follows:
testing a JSP based app on a WAS v5 server linking to an AS/400 RPG back
end; with 9 remote agents for the stress tests (currently running around 10
threads/agent).
We've done some investigation and for us it turns out that the threads were
hanging in the appserver: like you this was only experienced when using a
thread count in the hundreds - which is awkward as that's only a thread
count of 11 if, like us, you have 9 remote agents. Considering each box is
a dual 4ghz/5gb ram etc. that's quite annoying!
We're going to add dealys/waits to 'ape' human interraction, anyway, so with
any luck this may solve the problem as they're going to be random timings -
will let you know. Not sure if this [websphere etc] is another red-herring,
however.
Watch this space I guess?
Glad we're not alone ;-)
Cheers,
Al.
git wrote:
>
> Daniel,
>
> I would doubt that the thread.stop would cause any trouble anyway as it
> is caused by possible deadlocking between interdependent threads. Back
> in the late nineties when I first started messing with Java Threads was
> about the same time that native threads came in. Back the you could
> tell the JVM to use green threads (non native) or native. Under very
> heavy thread load, green threads were more stable.
>
> But - that was 8 years ago - and things have moved on. I have no idea
> if you can even use green threads any more.
>
> Cheers
>
> AJ
>
> On Mon, 2007-01-29 at 12:17 -0600, Daniel Kurtz wrote:
>
>> AJ;
>>
>> Well, as I mentioned the best that we've been able to work out so far is
>> to just limit the number of threads you run on one agent. Our target is
>> ultimately 500 users, and we're just going use 5 100-user agents to get
>> there, for this round at least.
>>
>> I'm not a Java developer, but I had a look at the source to see what's
>> going on when the "thread won't die" is being logged and found the
>> thread.stop. I thought I might have stumbled on something when I read in
>> the Java reference that thread.stop is considered unsafe and shouldn't be
>> used any more. But in looking further I've realized that this isn't where
>> the failure's occurring. These threads are already toast at this point.
>> They're so toasty the thread.stop can't even kill them, which is why
>> JMeter throws the message.
>>
>> Daniel Kurtz
>>
>>
>> ________________________________
>>
>> From: git [mailto:git@cubicalland.com]
>> Sent: Mon 1/29/2007 10:25 AM
>> To: JMeter Users List
>> Subject: RE: Thread won't die issue
>>
>>
>>
>> Daniel,
>>
>> I've seen this - but have no idea what causes it or what to do about it!
>>
>> You're not being ignored...
>>
>> Cheers
>>
>> AJ
>>
>> On Mon, 2007-01-29 at 09:40 -0600, Daniel Kurtz wrote:
>>
>> > Well, since no one responded to this I guess that no one else is seeing
>> it. What we're seeing here is that the threads are actually dying in some
>> way. They stop returning samples and for all practical intents and
>> purposes are 'hung' after that point. When we issue the 'stop' from the
>> console, JMeter sees all these threads still running and issues a
>> thread.stop command for each. It comes back a little later to each thread
>> to see if it has, indeed, stopped. It hasn't, so JMeter returns the
>> "thread won't die" message.
>> >
>> > What we've found is that, on any of the hardware we've tried it on
>> (which represents a pretty broad range of capabilities) this appears to
>> be related to an upper threshold on the number of threads that can be run
>> per agent. I place the figure at about 150, though for safety's sake
>> we're recommending to our users that they try not to go above 100 threads
>> per agent. That includes the console itself when running local tests.
>> >
>> > Daniel Kurtz
>> >
>> >
>> > ________________________________
>> >
>> > From: Daniel Kurtz [mailto:dkurtz@olenick.com]
>> > Sent: Mon 1/22/2007 11:10 AM
>> > To: jmeter-user@jakarta.apache.org
>> > Subject: Thread won't die issue
>> >
>> >
>> >
>> > We find that invariably we end up with more or less a number of threads
>> that don't go into an 'ending' status. Of course the test itself does not
>> end in these circumstances, but will just hang out there forever. When we
>> force a stop from the console, the end of jmeter.log ends up looking
>> like:
>> >
>> > ...
>> > 2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread
>> Group 1-500 is done
>> >
>> > 2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending
>> thread 499
>> >
>> > 2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread
>> Group 1-271
>> >
>> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread
>> won't die: Thread Group 1-271
>> >
>> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine:
>> Notifying test listeners of end of test
>> >
>> > 2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar:
>> setRunning(false,local)
>> >
>> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has
>> ended
>> >
>> > Suggestions as to what we should look at to resolve this?
>> >
>> > Thanks.
>> >
>> > Daniel Kurtz
>> >
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>> www.cubicalland.com
>> www.nerds-central.blogspot.com
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
> www.cubicalland.com
> www.nerds-central.blogspot.com
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Thread-won%27t-die-issue-tf3059035.html#a8845300
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Thread won't die issue
Posted by git <gi...@cubicalland.com>.
Daniel,
I would doubt that the thread.stop would cause any trouble anyway as it
is caused by possible deadlocking between interdependent threads. Back
in the late nineties when I first started messing with Java Threads was
about the same time that native threads came in. Back the you could
tell the JVM to use green threads (non native) or native. Under very
heavy thread load, green threads were more stable.
But - that was 8 years ago - and things have moved on. I have no idea
if you can even use green threads any more.
Cheers
AJ
On Mon, 2007-01-29 at 12:17 -0600, Daniel Kurtz wrote:
> AJ;
>
> Well, as I mentioned the best that we've been able to work out so far is to just limit the number of threads you run on one agent. Our target is ultimately 500 users, and we're just going use 5 100-user agents to get there, for this round at least.
>
> I'm not a Java developer, but I had a look at the source to see what's going on when the "thread won't die" is being logged and found the thread.stop. I thought I might have stumbled on something when I read in the Java reference that thread.stop is considered unsafe and shouldn't be used any more. But in looking further I've realized that this isn't where the failure's occurring. These threads are already toast at this point. They're so toasty the thread.stop can't even kill them, which is why JMeter throws the message.
>
> Daniel Kurtz
>
>
> ________________________________
>
> From: git [mailto:git@cubicalland.com]
> Sent: Mon 1/29/2007 10:25 AM
> To: JMeter Users List
> Subject: RE: Thread won't die issue
>
>
>
> Daniel,
>
> I've seen this - but have no idea what causes it or what to do about it!
>
> You're not being ignored...
>
> Cheers
>
> AJ
>
> On Mon, 2007-01-29 at 09:40 -0600, Daniel Kurtz wrote:
>
> > Well, since no one responded to this I guess that no one else is seeing it. What we're seeing here is that the threads are actually dying in some way. They stop returning samples and for all practical intents and purposes are 'hung' after that point. When we issue the 'stop' from the console, JMeter sees all these threads still running and issues a thread.stop command for each. It comes back a little later to each thread to see if it has, indeed, stopped. It hasn't, so JMeter returns the "thread won't die" message.
> >
> > What we've found is that, on any of the hardware we've tried it on (which represents a pretty broad range of capabilities) this appears to be related to an upper threshold on the number of threads that can be run per agent. I place the figure at about 150, though for safety's sake we're recommending to our users that they try not to go above 100 threads per agent. That includes the console itself when running local tests.
> >
> > Daniel Kurtz
> >
> >
> > ________________________________
> >
> > From: Daniel Kurtz [mailto:dkurtz@olenick.com]
> > Sent: Mon 1/22/2007 11:10 AM
> > To: jmeter-user@jakarta.apache.org
> > Subject: Thread won't die issue
> >
> >
> >
> > We find that invariably we end up with more or less a number of threads that don't go into an 'ending' status. Of course the test itself does not end in these circumstances, but will just hang out there forever. When we force a stop from the console, the end of jmeter.log ends up looking like:
> >
> > ...
> > 2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-500 is done
> >
> > 2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending thread 499
> >
> > 2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread Group 1-271
> >
> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread won't die: Thread Group 1-271
> >
> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
> >
> > 2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local)
> >
> > 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has ended
> >
> > Suggestions as to what we should look at to resolve this?
> >
> > Thanks.
> >
> > Daniel Kurtz
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
> www.cubicalland.com
> www.nerds-central.blogspot.com
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
www.cubicalland.com
www.nerds-central.blogspot.com
RE: Thread won't die issue
Posted by Daniel Kurtz <dk...@olenick.com>.
AJ;
Well, as I mentioned the best that we've been able to work out so far is to just limit the number of threads you run on one agent. Our target is ultimately 500 users, and we're just going use 5 100-user agents to get there, for this round at least.
I'm not a Java developer, but I had a look at the source to see what's going on when the "thread won't die" is being logged and found the thread.stop. I thought I might have stumbled on something when I read in the Java reference that thread.stop is considered unsafe and shouldn't be used any more. But in looking further I've realized that this isn't where the failure's occurring. These threads are already toast at this point. They're so toasty the thread.stop can't even kill them, which is why JMeter throws the message.
Daniel Kurtz
________________________________
From: git [mailto:git@cubicalland.com]
Sent: Mon 1/29/2007 10:25 AM
To: JMeter Users List
Subject: RE: Thread won't die issue
Daniel,
I've seen this - but have no idea what causes it or what to do about it!
You're not being ignored...
Cheers
AJ
On Mon, 2007-01-29 at 09:40 -0600, Daniel Kurtz wrote:
> Well, since no one responded to this I guess that no one else is seeing it. What we're seeing here is that the threads are actually dying in some way. They stop returning samples and for all practical intents and purposes are 'hung' after that point. When we issue the 'stop' from the console, JMeter sees all these threads still running and issues a thread.stop command for each. It comes back a little later to each thread to see if it has, indeed, stopped. It hasn't, so JMeter returns the "thread won't die" message.
>
> What we've found is that, on any of the hardware we've tried it on (which represents a pretty broad range of capabilities) this appears to be related to an upper threshold on the number of threads that can be run per agent. I place the figure at about 150, though for safety's sake we're recommending to our users that they try not to go above 100 threads per agent. That includes the console itself when running local tests.
>
> Daniel Kurtz
>
>
> ________________________________
>
> From: Daniel Kurtz [mailto:dkurtz@olenick.com]
> Sent: Mon 1/22/2007 11:10 AM
> To: jmeter-user@jakarta.apache.org
> Subject: Thread won't die issue
>
>
>
> We find that invariably we end up with more or less a number of threads that don't go into an 'ending' status. Of course the test itself does not end in these circumstances, but will just hang out there forever. When we force a stop from the console, the end of jmeter.log ends up looking like:
>
> ...
> 2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-500 is done
>
> 2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending thread 499
>
> 2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread Group 1-271
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread won't die: Thread Group 1-271
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
>
> 2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local)
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has ended
>
> Suggestions as to what we should look at to resolve this?
>
> Thanks.
>
> Daniel Kurtz
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
www.cubicalland.com
www.nerds-central.blogspot.com
RE: Thread won't die issue
Posted by git <gi...@cubicalland.com>.
Daniel,
I've seen this - but have no idea what causes it or what to do about it!
You're not being ignored...
Cheers
AJ
On Mon, 2007-01-29 at 09:40 -0600, Daniel Kurtz wrote:
> Well, since no one responded to this I guess that no one else is seeing it. What we're seeing here is that the threads are actually dying in some way. They stop returning samples and for all practical intents and purposes are 'hung' after that point. When we issue the 'stop' from the console, JMeter sees all these threads still running and issues a thread.stop command for each. It comes back a little later to each thread to see if it has, indeed, stopped. It hasn't, so JMeter returns the "thread won't die" message.
>
> What we've found is that, on any of the hardware we've tried it on (which represents a pretty broad range of capabilities) this appears to be related to an upper threshold on the number of threads that can be run per agent. I place the figure at about 150, though for safety's sake we're recommending to our users that they try not to go above 100 threads per agent. That includes the console itself when running local tests.
>
> Daniel Kurtz
>
>
> ________________________________
>
> From: Daniel Kurtz [mailto:dkurtz@olenick.com]
> Sent: Mon 1/22/2007 11:10 AM
> To: jmeter-user@jakarta.apache.org
> Subject: Thread won't die issue
>
>
>
> We find that invariably we end up with more or less a number of threads that don't go into an 'ending' status. Of course the test itself does not end in these circumstances, but will just hang out there forever. When we force a stop from the console, the end of jmeter.log ends up looking like:
>
> ...
> 2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-500 is done
>
> 2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending thread 499
>
> 2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread Group 1-271
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread won't die: Thread Group 1-271
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
>
> 2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local)
>
> 2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has ended
>
> Suggestions as to what we should look at to resolve this?
>
> Thanks.
>
> Daniel Kurtz
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
www.cubicalland.com
www.nerds-central.blogspot.com
RE: Thread won't die issue
Posted by Daniel Kurtz <dk...@olenick.com>.
Well, since no one responded to this I guess that no one else is seeing it. What we're seeing here is that the threads are actually dying in some way. They stop returning samples and for all practical intents and purposes are 'hung' after that point. When we issue the 'stop' from the console, JMeter sees all these threads still running and issues a thread.stop command for each. It comes back a little later to each thread to see if it has, indeed, stopped. It hasn't, so JMeter returns the "thread won't die" message.
What we've found is that, on any of the hardware we've tried it on (which represents a pretty broad range of capabilities) this appears to be related to an upper threshold on the number of threads that can be run per agent. I place the figure at about 150, though for safety's sake we're recommending to our users that they try not to go above 100 threads per agent. That includes the console itself when running local tests.
Daniel Kurtz
________________________________
From: Daniel Kurtz [mailto:dkurtz@olenick.com]
Sent: Mon 1/22/2007 11:10 AM
To: jmeter-user@jakarta.apache.org
Subject: Thread won't die issue
We find that invariably we end up with more or less a number of threads that don't go into an 'ending' status. Of course the test itself does not end in these circumstances, but will just hang out there forever. When we force a stop from the console, the end of jmeter.log ends up looking like:
...
2007/01/22 10:52:44 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-500 is done
2007/01/22 10:52:44 INFO - jmeter.engine.StandardJMeterEngine: Ending thread 499
2007/01/22 10:59:10 INFO - jmeter.threads.JMeterThread: Stopping Thread Group 1-271
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Thread won't die: Thread Group 1-271
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
2007/01/22 10:59:15 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local)
2007/01/22 10:59:15 INFO - jmeter.engine.StandardJMeterEngine: Test has ended
Suggestions as to what we should look at to resolve this?
Thanks.
Daniel Kurtz