Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Mon, 18 Jul 2016 21:06:20 +0000 (UTC)
From: "Nhan Thuan Nguyen (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12990551.1468874913000.64961.1468875980576@Atlassian.JIRA>
In-Reply-To: <JIRA.12990551.1468874913000@Atlassian.JIRA>
References: <JIRA.12990551.1468874913000@Atlassian.JIRA> <JIRA.12990551.1468874913780@arcas>
Subject: [jira] [Updated] (HTTPASYNC-107) Expired SSL connections are not
 getting closed.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 18 Jul 2016 21:06:23 -0000


     [ https://issues.apache.org/jira/browse/HTTPASYNC-107?page=3Dcom.atlas=
sian.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 K=
eep-Alive response header timeout=3D5 seconds. When a SSL connection on con=
nection pool expires, it tries to close the connection by sending an SSL AL=
ERT notify to the far end. The server does not respond to the alert and doe=
sn't close the connection. Since the connection has a socketTimeout set to =
0 onRelease(), the connection hangs forever. A socket is lost every time th=
is occurs. We're eventually running out of ephemeral ports and getting exce=
ption 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 h=
eader 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. Sin=
ce the connection has a socketTimeout set to 0 onRelease(), the connection =
hangs forever. A socket is lost every time this occurs. We're eventually ru=
nning out of ephemeral ports and getting exception Caused by: java.net.Bind=
Exception: 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 respo=
nse header timeout=3D5 seconds. When a SSL connection on connection pool ex=
pires, it tries to close the connection by sending an SSL ALERT notify to t=
he 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'r=
e 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