[
https://issues.apache.org/jira/browse/HTTPCLIENT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811570#comment-16811570
]
Dmytro TOLSTYI commented on HTTPCLIENT-1980:
--------------------------------------------
Hi [~olegk]. I've tried updating all the modules but it didn't help. I've also
tried to change proxy when issue occurs (to eliminate possible blocks from the
site side) = no result.
But, then I've tried closing client and creating a new instance as soon as
issue arises and it solved the problem. So, I'm receiving
SocketTimeoutException 5 times (I've set 5 retries in my program) and then new
client is being. When new client is created there are no more SocketTimeout
issues.
Does this look like HttpClient issue?
> 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, http2.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]
