[
https://issues.apache.org/jira/browse/HTTPCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392351#comment-15392351
]
Nhan Thuan Nguyen commented on HTTPCORE-427:
--------------------------------------------
When do I expect version 4.4.6 to be released?
> Expired SSL connections are not getting closed.
> -----------------------------------------------
>
> Key: HTTPCORE-427
> URL: https://issues.apache.org/jira/browse/HTTPCORE-427
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.4.5
> Reporter: Nhan Thuan Nguyen
> Fix For: 4.4.6, 5.0-alpha2
>
> Attachments: httpasync-107.log
>
>
> 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]