Hello, I'm using http client 5.2.3, with CloseableHttpAsyncClient and PoolingAsyncClientConnectionManager. I am sending POST requests using SimpleHttpRequest and SimpleHttpResponse. Occasionally I catch a "java.net.SocketException Connection Reset" exception. When I retry my code to send another POST request after the exception, I hit the same Connection Reset exception again. I don't know how to analyze it, but it seems to me that on the second call the http client re-uses the same connection that previously encountered the Connection Reset exception, instead of using a new one. Is this possible, or am I missing something? If so, what can I do to ensure that the second call uses a valid connection? Is there a way to forcibly close/evict a connection from the pool if I think that it is bad?
Thanks, Jonathan
