|Deletions are marked like this.||Additions are marked like this.|
|Line 68:||Line 68:|
Connection Reset since JMeter 2.10 ?
If you upgraded recently to JMeter 2.10 or 2.11, you may have noticed increased errors of this type:
- Socket closed
Non HTTP response code: org.apache.http.NoHttpResponseException (the target server failed to respond)
The increase of this type of errors can be explained by two settings changes:
- retry of failing request (idempotent ones only) has been disabled in JMeter 2.10
- stale check in HTTP Client 3 and 4 implementations has been disabled in JMeter 2.11
Why these changes?
Previous retry default settings led to increased number of Requests in certain type of failures.
Previous stale check was a bit expensive, as it applied to every sample. That is why the default was changed to disable it.
Retry or stale check can hide issues on Server configuration:
- Server failing to send the (optional) Keep-Alive header
- Overwhelmed server refusing connection, retrying would increase load
If you think this server behavior is OK, then configuration can be changed in two places:
For HttpClient 4, in user.properties set :
This will make JMeter retry once. For HttpClient 3, in user.properties set:
This will make JMeter retry once.
Enabling stale check
For HC4 Implementation:
In hc.parameters set:
For HC3 Implementation:
In httpclient.parameters set:
New setting in JMeter 2.12
Upcoming version of JMeter adds a setting to add an idle connection timeout if the server does not send Keep-Alive headers.
This value is in milliseconds:
httpclient4.idletimeout=<time in ms>
Scope of document
This article is about the increase of Socket closed error.
You may have this kind of issues even with retry and stale check enabled, in this case check server configuration and load.