You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Nhan Thuan Nguyen (JIRA)" <ji...@apache.org> on 2016/07/19 14:39:20 UTC
[jira] [Comment Edited] (HTTPASYNC-107) Expired SSL connections are
not getting closed.
[ https://issues.apache.org/jira/browse/HTTPASYNC-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384222#comment-15384222 ]
Nhan Thuan Nguyen edited comment on HTTPASYNC-107 at 7/19/16 2:38 PM:
----------------------------------------------------------------------
The connection expired, see line 36 in this log.
was (Author: nhan.thuan.nguyen):
The connection expired, see line 36 in this log.
2016-07-19 10:06:27,955 DEBUG [LmtpServer-2#1] CPoog- Connectiog[id:http-outgoing-0][route:{s}->https://api.abweb.aol.com:443][state:null] expired @ Tue Jul 19 10:05:22 EDT 2016
> 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
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org