You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Guillaume Lahitette <GL...@abingdon.oilfield.slb.com> on 2005/03/21 16:35:52 UTC
JMeter appears to be stuck
Hello folks,
I am testing a Tomcat webapp. In several instances, JMeter appears to be
stuck on one request and can not process with the next. I have enabled to
the DEBUG level but am not getting any more details in jmeter.log
In one scenario, I can see in the Tomcat access logs a failure that is
causing a servlet to return a response with status code = 200 but an empty
length.
Has any one seen such behavior?
Do I have a better solution than to put a time assertion of XYZ minutes on
each requests?
How can I tackle this issue?
This is JMeter 2.0.2 on Win 2K.
TIA for your precious help.
Guillaume
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: JMeter appears to be stuck
Posted by Guillaume Lahitette <GL...@abingdon.oilfield.slb.com>.
sebb,
I'm seeing 3 connections to that host that don't terminate, even after I
shut down JMeter. Not sure what else to conclude from this netstat...
glahitette@ABG-GLAHITETTE /cygdrive/D/espWatcherCVS
$ netstat -a|grep 28580
TCP ABG-GLAHITETTE:3117 slb-176-015.xxxx.com:28580 CLOSE_WAIT
TCP ABG-GLAHITETTE:3118 slb-176-015.xxxx.com:28580 CLOSE_WAIT
TCP ABG-GLAHITETTE:3119 slb-176-015.xxxx.com:28580 CLOSE_WAIT
Is there a time out setting that applies to all HTTP queries, regardless of
any Time Assertions?
Guillaume
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: 21 March 2005 17:13
> To: JMeter Users List
> Subject: Re: JMeter appears to be stuck
>
>
> Might be worth looking at netstat output on the JMeter and Tomcat nodes.
> This should show if Jmeter is still connected.
>
> If there are several JMeter threads, do the other threads continue OK?
>
>
> S.
> On Mon, 21 Mar 2005 10:22:58 -0600, Shane McCarron
> <sh...@aptest.com> wrote:
> > I have seen this behavior when jmeter had been running for a long time -
> > it appeared to be out of memory. Could that be the case here?
> >
> > Guillaume Lahitette wrote:
> >
> > >Hello folks,
> > >
> > >I am testing a Tomcat webapp. In several instances, JMeter
> appears to be
> > >stuck on one request and can not process with the next. I have
> enabled to
> > >the DEBUG level but am not getting any more details in jmeter.log
> > >
> > >In one scenario, I can see in the Tomcat access logs a failure that is
> > >causing a servlet to return a response with status code = 200
> but an empty
> > >length.
> > >
> > >Has any one seen such behavior?
> > >Do I have a better solution than to put a time assertion of
> XYZ minutes on
> > >each requests?
> > >How can I tackle this issue?
> > >
> > >This is JMeter 2.0.2 on Win 2K.
> > >
> > >TIA for your precious help.
> > >Guillaume
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: JMeter appears to be stuck
Posted by sebb <se...@gmail.com>.
Might be worth looking at netstat output on the JMeter and Tomcat nodes.
This should show if Jmeter is still connected.
If there are several JMeter threads, do the other threads continue OK?
S.
On Mon, 21 Mar 2005 10:22:58 -0600, Shane McCarron <sh...@aptest.com> wrote:
> I have seen this behavior when jmeter had been running for a long time -
> it appeared to be out of memory. Could that be the case here?
>
> Guillaume Lahitette wrote:
>
> >Hello folks,
> >
> >I am testing a Tomcat webapp. In several instances, JMeter appears to be
> >stuck on one request and can not process with the next. I have enabled to
> >the DEBUG level but am not getting any more details in jmeter.log
> >
> >In one scenario, I can see in the Tomcat access logs a failure that is
> >causing a servlet to return a response with status code = 200 but an empty
> >length.
> >
> >Has any one seen such behavior?
> >Do I have a better solution than to put a time assertion of XYZ minutes on
> >each requests?
> >How can I tackle this issue?
> >
> >This is JMeter 2.0.2 on Win 2K.
> >
> >TIA for your precious help.
> >Guillaume
> >
> >
>
> ---------------------------------------------------------------------
> 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: JMeter appears to be stuck
Posted by Guillaume Lahitette <GL...@abingdon.oilfield.slb.com>.
Mike,
The response information I mentioned is read from the Tomcat access logs. It
is the response that JMeter never sees / is stuck with.
Guillaume
> -----Original Message-----
> From: Michael Stover [mailto:mstover1@apache.org]
> Sent: 21 March 2005 18:40
> To: JMeter Users List
> Subject: RE: JMeter appears to be stuck
>
>
> If the problem is related to the http response coming back without
> length information, then some logging statements in HTTPSamplerBase
> might reveal at least where JMeter is getting blocked.
>
> -Mike
>
> On Mon, 2005-03-21 at 17:59 +0000, Guillaume Lahitette wrote:
> > Shane,
> >
> > No exceptions whatsoever in jmeter.log....Nada. Zip.
> >
> > In this case, JMeter doesn't run particularly long, a few
> minutes, 20 at max
> > before hitting this "freeze point".
> >
> > Guillaume
> >
> >
> > > -----Original Message-----
> > > From: Shane McCarron [mailto:shane@aptest.com]
> > > Sent: 21 March 2005 16:23
> > > To: JMeter Users List
> > > Subject: Re: JMeter appears to be stuck
> > >
> > >
> > > I have seen this behavior when jmeter had been running for a
> long time -
> > > it appeared to be out of memory. Could that be the case here?
> > >
> > > Guillaume Lahitette wrote:
> > >
> > > >Hello folks,
> > > >
> > > >I am testing a Tomcat webapp. In several instances, JMeter
> appears to be
> > > >stuck on one request and can not process with the next. I
> have enabled to
> > > >the DEBUG level but am not getting any more details in jmeter.log
> > > >
> > > >In one scenario, I can see in the Tomcat access logs a
> failure that is
> > > >causing a servlet to return a response with status code = 200
> > > but an empty
> > > >length.
> > > >
> > > >Has any one seen such behavior?
> > > >Do I have a better solution than to put a time assertion of XYZ
> > > minutes on
> > > >each requests?
> > > >How can I tackle this issue?
> > > >
> > > >This is JMeter 2.0.2 on Win 2K.
> > > >
> > > >TIA for your precious help.
> > > >Guillaume
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
>
>
>
> ---------------------------------------------------------------------
> 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: JMeter appears to be stuck
Posted by Michael Stover <ms...@apache.org>.
If the problem is related to the http response coming back without
length information, then some logging statements in HTTPSamplerBase
might reveal at least where JMeter is getting blocked.
-Mike
On Mon, 2005-03-21 at 17:59 +0000, Guillaume Lahitette wrote:
> Shane,
>
> No exceptions whatsoever in jmeter.log....Nada. Zip.
>
> In this case, JMeter doesn't run particularly long, a few minutes, 20 at max
> before hitting this "freeze point".
>
> Guillaume
>
>
> > -----Original Message-----
> > From: Shane McCarron [mailto:shane@aptest.com]
> > Sent: 21 March 2005 16:23
> > To: JMeter Users List
> > Subject: Re: JMeter appears to be stuck
> >
> >
> > I have seen this behavior when jmeter had been running for a long time -
> > it appeared to be out of memory. Could that be the case here?
> >
> > Guillaume Lahitette wrote:
> >
> > >Hello folks,
> > >
> > >I am testing a Tomcat webapp. In several instances, JMeter appears to be
> > >stuck on one request and can not process with the next. I have enabled to
> > >the DEBUG level but am not getting any more details in jmeter.log
> > >
> > >In one scenario, I can see in the Tomcat access logs a failure that is
> > >causing a servlet to return a response with status code = 200
> > but an empty
> > >length.
> > >
> > >Has any one seen such behavior?
> > >Do I have a better solution than to put a time assertion of XYZ
> > minutes on
> > >each requests?
> > >How can I tackle this issue?
> > >
> > >This is JMeter 2.0.2 on Win 2K.
> > >
> > >TIA for your precious help.
> > >Guillaume
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: JMeter appears to be stuck
Posted by Guillaume Lahitette <GL...@abingdon.oilfield.slb.com>.
Shane,
No exceptions whatsoever in jmeter.log....Nada. Zip.
In this case, JMeter doesn't run particularly long, a few minutes, 20 at max
before hitting this "freeze point".
Guillaume
> -----Original Message-----
> From: Shane McCarron [mailto:shane@aptest.com]
> Sent: 21 March 2005 16:23
> To: JMeter Users List
> Subject: Re: JMeter appears to be stuck
>
>
> I have seen this behavior when jmeter had been running for a long time -
> it appeared to be out of memory. Could that be the case here?
>
> Guillaume Lahitette wrote:
>
> >Hello folks,
> >
> >I am testing a Tomcat webapp. In several instances, JMeter appears to be
> >stuck on one request and can not process with the next. I have enabled to
> >the DEBUG level but am not getting any more details in jmeter.log
> >
> >In one scenario, I can see in the Tomcat access logs a failure that is
> >causing a servlet to return a response with status code = 200
> but an empty
> >length.
> >
> >Has any one seen such behavior?
> >Do I have a better solution than to put a time assertion of XYZ
> minutes on
> >each requests?
> >How can I tackle this issue?
> >
> >This is JMeter 2.0.2 on Win 2K.
> >
> >TIA for your precious help.
> >Guillaume
> >
> >
>
> ---------------------------------------------------------------------
> 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: JMeter appears to be stuck
Posted by Shane McCarron <sh...@aptest.com>.
I have seen this behavior when jmeter had been running for a long time -
it appeared to be out of memory. Could that be the case here?
Guillaume Lahitette wrote:
>Hello folks,
>
>I am testing a Tomcat webapp. In several instances, JMeter appears to be
>stuck on one request and can not process with the next. I have enabled to
>the DEBUG level but am not getting any more details in jmeter.log
>
>In one scenario, I can see in the Tomcat access logs a failure that is
>causing a servlet to return a response with status code = 200 but an empty
>length.
>
>Has any one seen such behavior?
>Do I have a better solution than to put a time assertion of XYZ minutes on
>each requests?
>How can I tackle this issue?
>
>This is JMeter 2.0.2 on Win 2K.
>
>TIA for your precious help.
>Guillaume
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org