Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 20937 invoked from network); 27 Jan 2005 19:12:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 Jan 2005 19:12:31 -0000 Received: (qmail 65647 invoked by uid 500); 27 Jan 2005 19:12:28 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 65620 invoked by uid 500); 27 Jan 2005 19:12:28 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 65606 invoked by uid 99); 27 Jan 2005 19:12:27 -0000 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of hsu.paul@verizon.net designates 206.46.170.137 as permitted sender) Received: from out012pub.verizon.net (HELO out012.verizon.net) (206.46.170.137) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 27 Jan 2005 11:12:26 -0800 Received: from hsuasus ([4.29.69.95]) by out012.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050127191224.WQGB10436.out012.verizon.net@hsuasus> for ; Thu, 27 Jan 2005 13:12:24 -0600 Message-ID: <004a01c504a4$2f691290$1400a8c0@hsuasus> From: "Paul Hsu" To: "Jakarta Commons Developers List" References: <002f01c50492$4616e8d0$1400a8c0@hsuasus> <41F936E9.9030507@pandora.be> Subject: Re: [DBCP] connection boorow time out Date: Thu, 27 Jan 2005 11:12:44 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authentication-Info: Submitted using SMTP AUTH at out012.verizon.net from [4.29.69.95] at Thu, 27 Jan 2005 13:12:23 -0600 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Dirk, Thank you. But I think the feature is deprecated? Can I still use it? Thanks, Paul ----- Original Message ----- From: "Dirk Verbeeck" To: "Jakarta Commons Developers List" Sent: Thursday, January 27, 2005 10:46 AM Subject: Re: [DBCP] connection boorow time out > You are looking for the "removeAbandoned" feature. > DBCP doesn't check periodically but only when the pool is almost empty. > More information on the configuration page: > http://jakarta.apache.org/commons/dbcp/configuration.html > > -- Dirk > > Paul Hsu wrote: > >> Hi, >> >> I just wonder that DBCP can monitor a connection pool to check if a >> connection is borrowed too long by a client periodically, if so then pool >> will mandatory move the connection from active to idle. This can void >> whoever borrow the connection and never return to pool. So we need to >> parameters can be set, one is the how often pool will monitor and other >> is how long a connection can be borrowed out. >> >> >> Thanks, >> >> Paul > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org