Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC86410B4D for ; Mon, 17 Feb 2014 11:15:37 +0000 (UTC) Received: (qmail 74539 invoked by uid 500); 17 Feb 2014 11:15:36 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 74302 invoked by uid 500); 17 Feb 2014 11:15:22 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 74292 invoked by uid 99); 17 Feb 2014 11:15:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Feb 2014 11:15:20 +0000 Date: Mon, 17 Feb 2014 11:15:19 +0000 (UTC) From: "Yoram Dayagi (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HTTPASYNC-69) calling IOControl.shutdown() doesn't release the underlying connection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Yoram Dayagi created HTTPASYNC-69: ------------------------------------- Summary: calling IOControl.shutdown() doesn't release the unde= rlying connection Key: HTTPASYNC-69 URL: https://issues.apache.org/jira/browse/HTTPASYNC-69 Project: HttpComponents HttpAsyncClient Issue Type: Bug Affects Versions: 4.0 Final Environment: MacBook Pro, OSX Reporter: Yoram Dayagi Below is the log of the following scenario: 1. Create an async client with MaxConnPerRoute=3D1 2. Start a request=20 3. Wait for 100ms and shutdown the channel (using ioctrl.shutdown) 4. Wait for 2000ms and start another request for same url 2014/02/17 12:34:15:587 IST [DEBUG] PoolingNHttpClientConnectionManager - C= onnection request: [route: {}->http://966b.http.dal05.cdn.softlayer.net:80]= [total kept alive: 0; route allocated: 0 of 1; total allocated: 0 of 10] 2014/02/17 12:34:15:681 IST [DEBUG] PoolingNHttpClientConnectionManager - C= onnection leased: [id: http-outgoing-0][route: {}->http://966b.http.dal05.c= dn.softlayer.net:80][total kept alive: 0; route allocated: 1 of 1; total al= located: 1 of 10] 2014/02/17 12:34:15:689 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][r:]: Set attribute h= ttp.nio.exchange-handler 2014/02/17 12:34:15:690 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][rw:]: Event set [w] 2014/02/17 12:34:15:691 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][rw:]: Set attribute = http.nio.http-exchange-state 2014/02/17 12:34:15:692 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][rw:]: Event set [w] 2014/02/17 12:34:15:694 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][rw:w]: 246 bytes wri= tten 2014/02/17 12:34:15:694 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][r:w]: Event cleared = [w] 2014/02/17 12:34:15:770 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][r:r]: 1360 bytes rea= d 2014/02/17 12:34:15:775 IST [DEBUG] ManagedNHttpClientConnectionImpl - http= -outgoing-0 10.0.0.2:58623<->93.184.221.133:80[ACTIVE][r:r]: Shutdown 2014/02/17 12:34:17:695 IST [DEBUG] PoolingNHttpClientConnectionManager - C= onnection request: [route: {}->http://966b.http.dal05.cdn.softlayer.net:80]= [total kept alive: 0; route allocated: 1 of 1; total allocated: 1 of 10] =20 Note that the last log of =E2=80=9CConnection request=E2=80=9D reports that= =E2=80=9Croute allocated: 1 of 1=E2=80=9D.=20 It probably means that the connection was not released when the channel was= shut down. >From the client perspective, the consumer=E2=80=99s onByteReceived is never= called after this point. -- This message was sent by Atlassian JIRA (v6.1.5#6160) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org