Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 82519 invoked from network); 15 Apr 2003 21:08:21 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 15 Apr 2003 21:08:21 -0000 Received: (qmail 28676 invoked by uid 97); 15 Apr 2003 21:10:20 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 28669 invoked from network); 15 Apr 2003 21:10:20 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 15 Apr 2003 21:10:20 -0000 Received: (qmail 81659 invoked by uid 500); 15 Apr 2003 21:08:13 -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 81585 invoked from network); 15 Apr 2003 21:08:13 -0000 Received: from pcow035o.blueyonder.co.uk (HELO blueyonder.co.uk) (195.188.53.121) by daedalus.apache.org with SMTP; 15 Apr 2003 21:08:13 -0000 Received: from localhost ([80.194.24.21]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.757.75); Tue, 15 Apr 2003 22:08:17 +0100 Date: Tue, 15 Apr 2003 22:09:06 +0100 Subject: Re: Production use of Connection Pooling Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: robert burrell donkin To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: <003801c30392$f040e840$6701a8c0@LAWLOR> Message-Id: <7E640446-6F86-11D7-A0CC-003065DC754C@blueyonder.co.uk> X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N hi frank you might get a better response if you remembered to prefix your subject with the name of the component. - robert On Tuesday, April 15, 2003, at 10:06 PM, Frank Lawlor wrote: > I thought I posted this a while ago, but can't find it in the archive, > so I'll try again: > > > > I just went through a project where we looked at using the commons > pooling in a production application. > > > > We found a number of serious problems with its use. Anyone considering > production use of the commons pooling or any pooling product should be > aware of these issues. > > > > We also documented some programming practices for using pooled > connections. > > > > To see these look in the White Papers section of > http://stealthis.athensgroup.com/presentations/ > > for Jakarta_Pooling.doc and Proper_JDBC.doc > > > > -- Frank > > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org