Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2D117C74A for ; Mon, 5 Jan 2015 13:48:36 +0000 (UTC) Received: (qmail 3324 invoked by uid 500); 5 Jan 2015 13:48:36 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 3275 invoked by uid 500); 5 Jan 2015 13:48:36 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 3261 invoked by uid 99); 5 Jan 2015 13:48:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2015 13:48:33 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of snicoll@pivotal.io does not designate 162.253.133.43 as permitted sender) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2015 13:48:08 +0000 Received: from mtom.nabble.com (unknown [162.253.133.81]) by mwork.nabble.com (Postfix) with ESMTP id 78250F8B96E for ; Mon, 5 Jan 2015 05:46:37 -0800 (PST) Date: Mon, 5 Jan 2015 06:44:56 -0700 (MST) From: "snicoll@pivotal.io" To: httpclient-users@hc.apache.org Message-ID: <1420465496332-25175.post@n7.nabble.com> In-Reply-To: <61A570E2FDBE0A4FB8F4EC8F764A9767C779D0@PARS1PZEXMBX003.mercury.intra> References: <61A570E2FDBE0A4FB8F4EC8F764A9767C776F7@PARS1PZEXMBX003.mercury.intra> <1418718920.26829.2.camel@apache.org> <61A570E2FDBE0A4FB8F4EC8F764A9767C777F1@PARS1PZEXMBX003.mercury.intra> <61A570E2FDBE0A4FB8F4EC8F764A9767C7784A@PARS1PZEXMBX003.mercury.intra> <61A570E2FDBE0A4FB8F4EC8F764A9767C7792C@PARS1PZEXMBX003.mercury.intra> <1418820247.9420.1.camel@apache.org> <61A570E2FDBE0A4FB8F4EC8F764A9767C779D0@PARS1PZEXMBX003.mercury.intra> Subject: RE: PoolingHttpClientConnectionManager leaking connections MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Please raise such issue on the Spring Framework issue tracker at http://jira.spring.io if you believe this is a bug in the Spring Framework. Hopefully, Francisco did report the issue based on this thread already: https://jira.spring.io/browse/SPR-12593 Could you please add a sample project that reproduces the issue over there? Thanks, S. -- View this message in context: http://httpcomponents.10934.n7.nabble.com/PoolingHttpClientConnectionManager-leaking-connections-tp25080p25175.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org