Is the driver in exactly one place -- $TOMCAT_HOME/common/lib? This is
the only place the driver is documented to work from. If the jar file
is in multiple places it can cause classloader issues. Related to that,
also check it isn't in any classpath or the JVM endorsed folder.
Did you restart tomcat between attempts?
As I recall, all JDBC drivers return a more or less generic
java.sql.Connection object so compatibility with the DBCP based pool is
a non-issue.
--David
Saurabh Nanda wrote:
ojdbc14.jar should be in $TOMCAT_HOME/common/lib to be available to both
the container and your webapp.
Nopes:
o Put it in $CATALINA_HOME/common/lib alone -- same error
o put it in webapps/appname/WEB-INf/lib and $CATALINE_HOME/common/lib,
both -- same error!
Does oracle drier support DBCP?
Nandz.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
