Java.net.SocketException connection reset error in .net application

前端 未结 4 1385
天涯浪人
天涯浪人 2020-12-21 14:13

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).

相关标签:
4条回答
  • 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:

    1. Change implementation of all your HTTP Request samplers to HTTPClient4. The best way to do it is via HTTP Request Defaults.
    2. 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
      
    3. In hc.parameters file (same location - /bin folder of your JMeter installation) add the next line:

      http.connection.stalecheck$Boolean=true
      
    4. Restart JMeter instance so it could read updated properties and restart your test.

    0 讨论(0)
  • 2020-12-21 14:52

    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.

    0 讨论(0)
  • 2020-12-21 15:00

    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
    
    0 讨论(0)
  • 2020-12-21 15:07

    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.

    0 讨论(0)
提交回复
热议问题