Hi Sebb,
Thanks for the fast reply.
I did check the documentation, but wasn't able to find the default
value for the response timeout.
I can try to set the Response Timeout in the HTTP Request Default to
30000 and see if the problem is still there.
Do you happen to know a way to find out what was the exact cause of
this error (server or network)? (I don't have access to the server logs)
Thanks,
Alex
On Sep 22, 2009, at 2:43 PM, sebb wrote:
On 22/09/2009, Alexandru Rotaru <[email protected]> wrote:
Hi all,
I am currently using JMeter 2.3.4 to execute some tests with 50 and
100
concurrent users.
Some of the samplers return:
Load time: 21249
Latency: 0
Size in bytes: 1661
Sample Count: 1
Error Count: 1
Response code: Non HTTP response code:
java.net.ConnectException
Response message: Non HTTP response message: Connection
timed out:
connect
For me this means that the client has waited too much for the server
response, but as I'm kinda new to JMeter I'm not 100% sure ...
This just means that JMeter did not get a response within the time
limit.
The cause is a server or network problem.
I executed the test both on a Windows machine and a Mac OS X, and I
got
this error on both of them.
Is there a default value for the timeout and can it be changed (the
load
time was in this case 21249 ms)?
The default depends on the Http stack (Java or HttpClient).
See
http://jakarta.apache.org/jmeter/usermanual/component_reference.html#HTTP_Request
"Response Timeout"
Thanks,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
