[
https://issues.apache.org/jira/browse/HTTPASYNC-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nhan Thuan Nguyen updated HTTPASYNC-107:
----------------------------------------
Description: We have a case where the far end server returns the HTTP
Keep-Alive response header timeout=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. (was: 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.)
> 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 timeout=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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
