hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nhan Thuan Nguyen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPASYNC-107) Expired SSL connections are not getting closed.
Date Mon, 18 Jul 2016 20:49:20 GMT
Nhan Thuan Nguyen created HTTPASYNC-107:

             Summary: Expired SSL connections are not getting closed.
                 Key: HTTPASYNC-107
                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-107
             Project: HttpComponents HttpAsyncClient
          Issue Type: Bug
    Affects Versions: 4.1.1
            Reporter: Nhan Thuan Nguyen

We have a case where the far end server returns the HTTP Keep-Alive response header 5 seconds.
When a SSL connection on connection pool expires, it tries to close the connection by sending
an SSL ALERT notify to the far end. The server does not respond to the alert and doesn't close
the connection. Since the connection has a socketTimeout set to 0 onRelease(), the connection
hangs forever. A socket is lost every time this occurs. We're eventually running out of ephemeral
ports and getting exception Caused by: java.net.BindException: Address already in use.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message