[
https://issues.apache.org/jira/browse/HTTPCLIENT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810620#comment-16810620
]
Dmytro TOLSTYI commented on HTTPCLIENT-1980:
--------------------------------------------
This is actually what I do. I just retry the request several times. But, as you
can see, the connection gets closed and I'm still trying to send requests
without any success. Isn't there any mechanism to identify that connection was
closed and reopen it? Or should I create a new instance of HttpClient?
> HttpClient continues to use connection that was already closed
> (SocketTimeoutException)
> ---------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1980
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1980
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (async)
> Affects Versions: 4.5.8
> Environment: Linux
> Reporter: Dmytro TOLSTYI
> Priority: Major
> Attachments: http.zip
>
>
> I'm using HttpClient for long-run activities (several weeks) and often it
> happens that the connection gets closed and HttpClient still sends requests
> using it. As a result I'm receiving `java.net.SocketTimeoutException: null`.
>
> Is there any possibility to manually reopen closed connection?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
