Question

I am seeing a problem with reusing my http-client after an HttpPost’s execute fails. It can be a timeout or service not available (maybe others). The request might throw a socket-timeout and when i later use the client (with a new HttpPost object) it will throw an illegal state exception. My research indicates that this occurs when the socket is not marked for “reuse” as in the case that naturally occurs if you have two threads and one is in the middle of processing its request before the second thread tries to use the http-client (hence its socket).

I think there is a bug in the http-client code, but there could be either some ‘best practises’ that I am not following correctly or some known work around.

Any help on this would be appreciated.

Answer 1

My research indicates that this occurs when the socket is not marked for “reuse” as in the case that naturally occurs if you have two threads and one is in the middle of processing its request before the second thread tries to use the http-client (hence its socket).

HttpClient is not thread-safe by default. You need to use a ThreadSafeClientConnManager.