[
https://issues.apache.org/jira/browse/HTTPCLIENT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809617#comment-16809617
]
Oleg Kalnichevski commented on HTTPCLIENT-1980:
-----------------------------------------------
bq. So, what I see is that HttpClient is trying to send requests to client and
receives `SocketTimeoutException` when `netstat` shows that there are no
connections for this process.
Well, looks like the JRE is doing something funny. Low level socket I/O
operations are handled by the Java runtime, not HttpClient. Most likely the
connection looks open and alive to the connection manager used by HttpClient.
You have not disabled the state connection check in your application code by
any chance?
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]
