Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 20529 invoked from network); 23 Jul 2003 14:23:42 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 23 Jul 2003 14:23:42 -0000 Received: (qmail 5289 invoked by uid 97); 23 Jul 2003 14:26:16 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 5282 invoked from network); 23 Jul 2003 14:26:15 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 23 Jul 2003 14:26:15 -0000 Received: (qmail 20344 invoked by uid 500); 23 Jul 2003 14:23:39 -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 20324 invoked from network); 23 Jul 2003 14:23:38 -0000 Received: from web20704.mail.yahoo.com (216.136.226.177) by daedalus.apache.org with SMTP; 23 Jul 2003 14:23:38 -0000 Message-ID: <20030723142338.89237.qmail@web20704.mail.yahoo.com> Received: from [32.97.110.142] by web20704.mail.yahoo.com via HTTP; Wed, 23 Jul 2003 07:23:38 PDT Date: Wed, 23 Jul 2003 07:23:38 -0700 (PDT) From: David Graham Reply-To: dgraham@apache.org Subject: Re: [DBCP] AbandonedTrace - Connection Recovery To: Jakarta Commons Developers List In-Reply-To: <3F1E96C1.5080508@mail.more.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I am really getting tired of the 'purists' in this discussion telling > the 'realists', "Just fix your code". > > That is not the issue at all. Those who are advocating to retain this > feature are doing so from an application server admin perspective. > When I have had to deal with this problem as the application server > admin there are many times when I don't even have access to the code. > Its the customers code. > > And yes, my organization does provide our customers with guidelines > with Do's and Dont's when writing web applications which includes a > discussion of db connection pooling and how to make sure the > db connection is closed properly. Do you also have a policy for what the consequences are for apps that leak resources? I still see this as outside DBCP's scope. Adding kludges to DBCP is really not the best way to solve this problem. David > > Regards, > > Glenn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org