[
https://issues.apache.org/jira/browse/HTTPCLIENT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809636#comment-16809636
]
Oleg Kalnichevski commented on HTTPCLIENT-1980:
-----------------------------------------------
{quote}The one thing I use is proxy. Not sure if this can be the issue.
{quote}
So, what connection goes bad? Client to proxy or proxy to origin? What is the
client doing at that point? Please do provide a log of the session as described
here:
[http://hc.apache.org/httpcomponents-client-4.5.x/logging.html]
Oleg
> 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
>
> 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]
