HttpClient executeMethod throws java.net.SocketException: Connection reset

Question

I have a java program which creates multiple threads where each thread makes POST request. It works fine most of the time but under heavy load it throws Connection reset exception. For example, when I made 40 simultaneous requests, couple of time I got Connection reset exception.

Caught: java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
   at java.net.SocketInputStream.read(SocketInputStream.java:168)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
   at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:
   at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105
   at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.
   at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMetho
   at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodB
   at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.j
   at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Htt
   at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMe
   at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav
   at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav

In my Java code, I am creating an instance of HttpClient

HttpClient client = new HttpClient();

The problem does not happen when I make one request wait for it to finish and then make another request. However, the moment I turn the program into multi-threading I get this issue.

Could anyone please point out how could I prevent this exception and then retry again. From google, I found out the answer may be along the lines of using

org.apache.commons.httpclient.util.IdleConnectionTimeoutThread

I am trying to use this in the mean time but any other suggestions are welcome.

Is there any logging server side which might give you a clue as to why this is happening? — Nattrass
– Nattrass, Commented Oct 20, 2014 at 20:45

hooknc · Accepted Answer · 2016-09-28 21:44:40Z

3

I recommend either using a MultiThreadedHttpConnectionManager if you're using HttpClient 3 or PoolingHttpClientConnectionManager if you're using HttpClient 4.

I'm fairly confident that the default connection manager for both HttpClient 3 and HttpClient 4 are expecting only single thread access.

edited Sep 28, 2016 at 21:44

answered Oct 20, 2014 at 20:49

hooknc

5,0055 gold badges36 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Prabhjot Over a year ago

Thanks. I changed it to use MultiThreadedHttpConnectionManager and that solved the issue of Connection reset. I want to vote for your answer but unfortunately I don't have 15 reputation.

hooknc Over a year ago

I think you should be able to accept the answer though. Glad it worked out. :)

Collectives™ on Stack Overflow

HttpClient executeMethod throws java.net.SocketException: Connection reset

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related