You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Dmytro TOLSTYI (JIRA)" <ji...@apache.org> on 2019/04/04 08:14:00 UTC

[jira] [Created] (HTTPCLIENT-1980) HttpClient continues to use connection that was already closed (SocketTimeoutException)

Dmytro TOLSTYI created HTTPCLIENT-1980:
------------------------------------------

             Summary: 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


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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org