The "normal method" uses DriverManager.getConnection() which appears to
cast a wider net in resolving database URLs. Maybe someone who's seen
the DriverManager class source can comment?
--David
Saurabh Nanda wrote:
Thanks. I got it working:
1. Removed the oracle driver from WEB-INF/lib and
Thanks. I got it working:
1. Removed the oracle driver from WEB-INF/lib and put it in common/lib
2. Used the format of the URL given below:
jdbc:oracle:thin:@address:port:schema
-- but it's rather strange -- is this documented anywhere? When I was using
the "normal" (non DBCP) method to connect t
n or copying of it or its
contents
- Original Message -
From: "DE VINZELLES, Guillaume (ext.)" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Tuesday, October 17, 2006 11:18 AM
Subject: RE: Database connection pooling errors in Tomcat 5.5.17
Her
Guillaume (ext.)" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Tuesday, October 17, 2006 11:18 AM
Subject: RE: Database connection pooling errors in Tomcat 5.5.17
Here is a valid url :
url="jdbc:oracle:thin:@address:port:schema"
Guillaume de Vinzelles
DSI/PFS
: Tomcat Users List
Objet : Re: Database connection pooling errors in Tomcat 5.5.17
Some fishing through source and online -- your problem can happen if the
connection url is not recognized by the driver.
I was looking at the jdbc url you first posted:
jdbc:oracle:thin:[EMAIL PROTECTED] This doe
Some fishing through source and online -- your problem can happen if the
connection url is not recognized by the driver.
I was looking at the jdbc url you first posted:
jdbc:oracle:thin:[EMAIL PROTECTED] This doesn't come up as a valid form in any
online docs I can find. You might want to ve
14:13
À : Tomcat Users List
Objet : Re: Database connection pooling errors in Tomcat 5.5.17
> 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/appn
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 resta
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?
N
I think I see the problem...
ojdbc14.jar should be in $TOMCAT_HOME/common/lib to be available to both
the container and your webapp.
.jar files are always stored in a lib folder. Relative to tomcat's home
dir -- shared/lib, common/lib. Relative to the webapp -- WEB-INF/lib
--David
Saurab
This is the complete stacktrace of the error if it helps. The
ojdbc14.jar file is in the WEB-INF/classes directory.
SEVERE: Servlet.service() for servlet test threw exception
java.lang.NullPointerException
at
org.apache.tomcat.dbcp.dbcp.DelegatingConnection.close(DelegatingConnection.java
One other thought I just had. I don't use the Oracle driver, so bear
with me. Is there ever a case where the Oracle driver might return a
null connection instead of throwing an exception?
David Smith wrote:
Looks like the connection the pool is attempting to return is null.
Are there any e
Looks like the connection the pool is attempting to return is null. Are
there any errors further up the logs that might indicate an other issue
that might be causing this? For what it's worth, the code and config
posted look good.
--David
Saurabh Nanda wrote:
Hi,
I'm trying to configure
13 matches
Mail list logo
