Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 18311 invoked from network); 30 Sep 2002 17:36:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Sep 2002 17:36:29 -0000 Received: (qmail 11394 invoked by uid 97); 30 Sep 2002 17:36:57 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 11358 invoked by uid 97); 30 Sep 2002 17:36:56 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 11346 invoked by uid 98); 30 Sep 2002 17:36:56 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: "Boris Schroder" To: Subject: How do Datasources handle dis- and re-connects from a DB? Date: Mon, 30 Sep 2002 13:36:23 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Does anyone know how a connection pooled datasource is handling the situation where the database becomes temporarily unavailable? I would like the datasource to automatically re-establish the connection pool once the DB is available again. Is that somehow possible? The system I am using is: tomcat 4.0.4 with updated commons-xxx jars (collections,dbcp,pool) and removed tyrex0.9.7 My server.xml is identical to the one recommended in the docs for tomcat.4.1 Boris borisschroder@yahoo.com -- To unsubscribe, e-mail: For additional commands, e-mail: