Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 98106 invoked from network); 20 Nov 2004 23:41:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Nov 2004 23:41:03 -0000 Received: (qmail 18667 invoked by uid 500); 20 Nov 2004 23:40:59 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 18630 invoked by uid 500); 20 Nov 2004 23:40:58 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 18611 invoked by uid 99); 20 Nov 2004 23:40:58 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=EXCUSE_3 X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [140.142.33.20] (HELO mxout6.cac.washington.edu) (140.142.33.20) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 20 Nov 2004 15:40:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAKNeqfx027194 for ; Sat, 20 Nov 2004 15:40:52 -0800 Received: from [10.0.1.2] (pool-68-239-6-91.bos.east.verizon.net [68.239.6.91]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAKNeobw010257 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Sat, 20 Nov 2004 15:40:51 -0800 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <419DC444.7050401@bibit.com> References: <419DC444.7050401@bibit.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9A8262F4-3B4D-11D9-A00B-00306557E112@u.washington.edu> Content-Transfer-Encoding: 7bit From: Michael Becke Subject: Re: [HttpClient] Lifetime of an unused connection Date: Sat, 20 Nov 2004 18:40:47 -0500 To: "Jakarta Commons Users List" X-Mailer: Apple Mail (2.619) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Tom, In HttpClient 2.0 connections are never closed/deleted from a MultiThreadedHttpConnectionManager until it is shutdown. Things like keep-alive settings and exceptions will cause connections to be closed, but they will still be returned to the connection manager. HttpClient 3.0 (just about to be 3.0 beta1) adds the ability to close idle connections. Have a look at the following for some more details: and Mike On Nov 19, 2004, at 5:00 AM, Tom van den Berge wrote: > Hi, > > When using a MultiThreadedHttpConnectionManager for an HttpClient, > connections that are used and released again are placed back in the > pool again, so they can be reused. I was wondering for how long unused > connections will remain in the pool. In other words, what is causing a > connection to be removed from the pool? > > I can imagine it might be caused by the read timeout of the socket, or > there may be a separate 'keep alive' setting? Also the remote host > might terminate the connection after some time, and how does that > influence the connection object in the pool? > > I'm talking about httpclient 2.0.2. > > Thanks, > Tom > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org