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] [Commented] (HTTPCORE-427) Expired SSL connections are not getting closed.
Date Mon, 25 Jul 2016 17:33:20 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392349#comment-15392349

Nhan Thuan Nguyen commented on HTTPCORE-427:

Thank you Oleg. It works.

Just a quick question, why didn't you use the socket timeout setting from request config?

> 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

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

View raw message