Connection/Response timeout values don't seem to take effect in JMeter

Question

I am getting 'Non HTTP response message: Connection timed out: connect' for some HTTP requests so I tried to set the connection/response timeout value to 2 minutes (which is more than the connect time required for failing HTTP requests). To do this, I updated "HTTP Request Defaults" and added 120000 as Connect and Response Timeouts.

HTTP Request Defaults timeouts

[ HTTP Request Defaults timeouts[1]

However, when I run the test again, the HTTP requests still gave the same error. The sample result is as follows -

Load time: 21007
Connect Time: 21007
Latency: 0
Size in bytes: 2212
Sent bytes:0
Headers size in bytes: 0
Body size in bytes: 2212
Sample Count: 1
Error Count: 1
Data type ("text"|"bin"|""): text
Response code: Non HTTP response code: java.net.ConnectException
Response message: Non HTTP response message: Connection timed out: connect

It looks like the timeout value I set in HTTP request Defaults is not getting used here. I also tried to set the value of httpclient.timeout=120000 in jmeter.properties but no change. Have I missed something?

Can somebody please help me with this?

Thanks.

Edit - I have multiple HTTP requests and each run, different requests time-out. Here is one of the HTTP requests -

Updates:

I tried changing the Timeouts values in HTTP Request Defaults to very low (2000) to see how HTTP requests work. In this case, I was getting different error for requests exceeding connection time of 2000ms -

Non HTTP response code: org.apache.http.NoHttpResponseException/Non HTTP response message: : failed to respond

So I think changing the timeout values is not affecting my original error -

Non HTTP response code: java.net.ConnectException/Non HTTP response message: Connection timed out: connect

What is the difference between these two message?

Naveen Kumar R B Naveen Kumar R B · Accepted Answer · 2017-02-21T05:55:40

The issue seems more of a server configuration of connection timeout than client side configuration of connection timeout, though both must be configured appropriately.

Default connectionTimeout in tomcat server is 20 seconds. and you request is failed due to connection timeout at 21 seconds. so, though you configured at client side (120000) you must configure appropriately at server side as well, otherwise, server forces to close the connection attempt and raises Connect Timeout exception.

Reference:

The HTTP Connector (refer connectionTimeout attribute)

Connection/Response timeout values don't seem to take effect in JMeter

HTTP Request Defaults timeouts

2 Answers