RE: Can the JNDI Connection Pool re-connect after failure?

[Raible, Matt]

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:[EMAIL PROTECTED]]
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]