Yes,
and it works with standalone Tomcat, just not when coming in through Apache(WARP):
<Resource name="jdbc/tatepool" scope="Shareable"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/tatepool">
<parameter>
<name>validationQuery</name>
<value>select 1 from dual</value>
</parameter>
<parameter>
<name>user</name>
<value>myuser</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:oracle:thin:myuser@mynode:1521:myinstance</value>
</parameter>
<parameter>
<name>password</name>
<value>mypassword</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
</ResourceParams>
Any ideas?
-----Original Message-----
From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 04, 2002 10:05 AM
To: 'Jakarta Commons Users List'
Subject: RE: Problems when using Apache with DBCP
Troy Campano wrote:
> 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)
>
> Any ideas why it cannot find the JDBC driver when using WARP?
It's hard to say precisely what the problem is, but it looks like a misconfiguration.
For some reason, BasicDataSource.driverClassName must be null. Have you set the
driverClassName parameter in your server.xml?
(http://jakarta.apache.org/tomcat/tomcat-4.0-doc/jndi-resources-howto.html)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
