Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 568 invoked from network); 20 Feb 2006 01:22:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Feb 2006 01:22:20 -0000 Received: (qmail 90889 invoked by uid 500); 20 Feb 2006 01:22:16 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 90870 invoked by uid 500); 20 Feb 2006 01:22:16 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 7750 invoked by uid 99); 19 Feb 2006 13:41:46 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) To: commons-user@jakarta.apache.org Subject: [dbcp] Anyone who knows how the connection pool is closed upon server shutdown? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006 Message-ID: From: lekkim@heisterberg.dk Date: Sun, 19 Feb 2006 14:42:19 +0100 X-MIMETrack: Serialize by Notes Client on Mikkel Heisterberg/Partnere/It-Inspiration(Release 7.0.1|January 17, 2006) at 19-02-2006 14:42:23, Serialize complete at 19-02-2006 14:42:23 Content-Type: multipart/alternative; boundary="=_alternative 004B4920C125711A_=" X-Virus-Scanned: amavisd-new at itu.dk X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, hits=-5.665 tagged_above=-999 required=1 tests=[ALL_TRUSTED=-3.3, BAYES_00=-2.599, HTML_20_30=0.226, HTML_MESSAGE=0.001, NO_REAL_NAME=0.007] X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 004B4920C125711A_= Content-Type: text/plain; charset="US-ASCII" Hi there, I writing a custom connection pool for a project under Tomcat (written as the dbcp using the javax.naming.spi.ObjectFactory interface). The connection pool doesn't implement the javax.sql.DataSource interface. For the connection pool I need some lifecycle management and in that regard I was wondering how dbcp makes sure all the connections are closed when the application server shuts down. I can see from the source that the org.apache.commons.dbcp.BasicDataSource class has a close() method but I cannot see how it is called upon server termination. Does any of you guys know? Mikkel Heisterberg --=_alternative 004B4920C125711A_=--