Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 22088 invoked from network); 19 Aug 2003 23:32:03 -0000 Received: from nat1.sjc.collab.net (HELO localhost.localdomain) (208.185.179.4) by daedalus.apache.org with SMTP; 19 Aug 2003 23:32:03 -0000 Received: from localhost (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id AF20043497 for ; Tue, 19 Aug 2003 09:36:06 -0700 (PDT) Subject: RE: dbcp bug From: John McNally To: Jakarta Commons Developers List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 19 Aug 2003 09:36:06 -0700 Message-Id: <1061310966.1572.398.camel@localhost.localdomain> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 2003-08-19 at 01:24, KNOX, Liam, FM wrote: > Noel > > I took the latest snap shot and this seems to work fine. Is there a plan for > a new release in the near future? I am also interested in how dbcp deals > with closed or 'stale' > connections i.e. in the event of a db outage. Is it possible that stale > connections > could remain in the pool ? > It is possible to configure a pool to verify the connection before handing it out (or at other times, if less critical). Connections that don't pass the verification test (usually a simple sql query) are removed from the pool. john mcnally