Return-Path: 
 <tomcat-user-return-50708-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 30486 invoked from network); 29 Jan 2003 14:13:36 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 29 Jan 2003 14:13:36 -0000
Received: (qmail 19794 invoked by uid 97); 29 Jan 2003 14:15:01 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 19782 invoked from network); 29 Jan 2003 14:15:01 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 29 Jan 2003 14:15:01 -0000
Received: (qmail 25488 invoked by uid 500); 29 Jan 2003 14:12:00 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 25473 invoked from network); 29 Jan 2003 14:12:00 -0000
Received: from coral.tci.com (HELO snowmass.tci.com) (198.178.8.81)
  by daedalus.apache.org with SMTP; 29 Jan 2003 14:12:00 -0000
Received: from mms02-relaya.tci.com (mms02-relaya.broadband.att.com
 [147.191.89.206])
	by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h0TEC1st001173
	for <tomcat-user@jakarta.apache.org>; Wed, 29 Jan 2003 07:12:01 -0700 (MST)
Received: from 147.191.90.10 by mms02-RelayB.tci.com with ESMTP (
 Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Wed, 29 Jan 2003 07:11:58
 -0600
Received: by entexchimc03.broadband.att.com with Internet Mail Service (
 5.5.2653.19) id <DKV35YAL>; Wed, 29 Jan 2003 07:10:46 -0700
Message-ID: <41669DC6FE3B80449A33A4DD46DB370A0137BDC2@Entcoexch15>
From: "Raible, Matt" <Matt_Raible@cable.comcast.com>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Subject: RE: Can the JNDI Connection Pool re-connect after failure?
Date: Wed, 29 Jan 2003 07:11:30 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-WSS-ID: 12293EA41014711-01-01
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
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've tried adding the following and I still have the same problem as Ryan.  
        <parameter>
            <name>validationQuery</name>
            <value>SELECT 1 FROM DUAL</value>
        </parameter>

When I check my 4.1.18 Tomcat server every morning I get:

WARN [Ajp13Processor[11009][7]] JDBCExceptionReporter.logExceptions(35) |
SQL Error: 0, SQLState: null
ERROR [Ajp13Processor[11009][7]] JDBCExceptionReporter.logExceptions(42) |
Cannot load JDBC driver class 'null'
WARN [Ajp13Processor[11009][7]] SessionFactoryImpl.<init>(163) | Could not
obtain connection metadata
java.sql.SQLException: Cannot load JDBC driver class 'null'
        at
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.jav
a:529)
        at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:3
12)
        at
cirrus.hibernate.connection.DatasourceConnectionProvider.getConnection(Datas
ourceConnectionProvider.java:56)

Could this be from closing connections in a finally block?  This should just
return them to the pool right?

Thanks,

Matt

> -----Original Message-----
> From: Nikola Milutinovic [mailto:Nikola.Milutinovic@ev.co.yu]
> Sent: Wednesday, January 29, 2003 2:09 AM
> To: Tomcat Users List
> Subject: Re: Can the JNDI Connection Pool re-connect after failure?
> 
> 
> Boris Folgmann wrote:
> > Ryan Cornia wrote:
> > 
> > 
> >>Anyone using JNDI datasources that reconnect in case of a 
> lost link to
> >>the DB server?
> >>
> >>Any examples? I'm using the I-net driver for Oracle
> > 
> > 
> > Interesting question. In fact I have the same problem, 
> using DBCP and
> > PostgreSQL. I looked trough the Javadocs at
> > http://jakarta.apache.org/commons/dbcp/api/index.html
> > but did not find a resource argument for configuring 
> something like a
> > reconnect. Any comments welcome.
> 
> I believe that if you set up "connection verification query" 
> in your DataSource 
> definition in server.xml it will reconnect. Haven't tried it, though.
> 
> Nix.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org