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
|