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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
