[
https://issues.apache.org/jira/browse/HTTPCLIENT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810634#comment-16810634
]
Dmytro TOLSTYI commented on HTTPCLIENT-1980:
--------------------------------------------
[~olegk] That's interesting, I never thought that it might be JRE issue.
Actually, I never had this issue on Windows but it often appears on Linux (with
OpenJDK). I'll try to eliminate proxy from my setup and see the issue.
So, as far as I understood, there's no automatic mechanism to reopen
SocketTimeouted connections (which makes sense) but is it possible to do it
manually? Because the only way I see is just creating 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]
