If you upgraded recently to JMeter 2.10 or 2.11, you may have noticed increased errors of this type:
The increase of this type of errors can be explained by two settings 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:
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.
For HC4 Implementation:
In user.properties:
In hc.parameters set:
For HC3 Implementation:
In user.properties:
In httpclient.parameters set:
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:
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.