We have a n-tier (.net) web application where we have a Web tier -> App tier -> Database.
Everything worked fine until we went for load testing (using jmeter).
If you're absolutely sure that it is nothing wrong with your server and the problem is on JMeter side you can try following steps from Connection Reset since JMeter 2.10 ? wiki page, to wit:
HTTPClient4
. The best way to do it is via HTTP Request Defaults.Add the next 2 lines to user.properties file (lives under /bin folder of your JMeter installation):
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
In hc.parameters file (same location - /bin folder of your JMeter installation) add the next line:
http.connection.stalecheck$Boolean=true
Restart JMeter instance so it could read updated properties and restart your test.
Your server is most probably overloaded as a result of your load test.
So it starts rejecting connections which appear as Connection Reset error.
So 3 options:
your load profile is too aggressive based on real traffic
your load profile is ok, your server is not correctly configured or undersized
your application cannot handle this load
You can check this by slowing rampup to see when you start facing issues.
If I am performing a distributed testing, should I do the following steps on all my slave systems as well, not to get the "connection reset" error..?
Add the next 2 lines to user.properties file (lives under /bin folder of your JMeter installation):
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
In hc.parameters file (same location - /bin folder of your JMeter installation) add the next line:
http.connection.stalecheck$Boolean=true
IIS logs were helpful in digging into the root cause. We found that there were network connection exceptions in all the request where we were facing Socket issues.