Thanks for telling me about your issue. I experimented unsuccessfully with
different locations for the jar files in Tomcat 6.
Glassfish v2 is now stable. I was able to use that without running into
the JNDI problems that I had with Tomcat 6.
Paul Anderson-12 wrote:
Hi,
I had a problem
I added:
org.apache.naming.level=FINE
org.apache.tomcat.dbcp.level=FINE
to the bottom of my TC_HOME/conf/logging.properties, but the logging output
didn't change. Is there something else that needs to be changed to enable
logging?
Here's the complete log file below:
Oct 8, 2007 2:58:03 PM
Hi,
I had a problem before with this upgrade scenario using the Oracle
drivers, and asked the list. I was asked if the JAR was in
$CATALINA_HOME/lib - it was - no further ideas.
I have never had a problem before with JDK 4 or 5 on TC5.5, just with
JDK6 and TC6, so I temporarily abandoned my
hibernate is using the org.apache.commons.dbcp pool, so you need to
configure that one, or tell hibernate to use tomcat's pool
the clue here is, that tomcat's connection pool (while the same as
commons.dbcp) has the package renamed to org.apache.tomcat.dbcp.
this is a hibernate problem, your
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so now it's using
org.apache.tomcat.dbcp.dbcp.BasicDataSource, but I get a similar error.
I'm not sure what's wrong. I did notice that Tomcat 6 uses tomcat-dbcp
instead of commons-dbcp.
ok, that's a good start. take a look at this
Caused by: java.sql.SQLException: No suitable driver
did you put the .jar file for the JDBC driver in TC_HOME/lib?
Filip
aku1234 wrote:
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so
Yes. Anything else I should look at?
Filip Hanik - Dev Lists wrote:
ok, that's a good start. take a look at this
Caused by: java.sql.SQLException: No suitable driver
did you put the .jar file for the JDBC driver in TC_HOME/lib?
Filip
aku1234 wrote:
I did some investigation and
aku1234 wrote:
Yes. Anything else I should look at?
As Filip pointed out, without a driver you'll go nowhere. This would
appear to be the immediate issue to deal with.
What driver jar did you put in the lib dir?
Is there another copy in your WEB-INF/lib? You must remove that one if
there is.
I double checked everything. There is an ojdbc.jar file in TC_HOME/lib
and nowhere else.
I'm not sure that it even knows what driver it's trying to load.
The top part of the stacktrace was:
Cannot create JDBC driver of class '' for connect URL 'null'
Augustin
aku1234 wrote:
Yes.
yeah, but you are not using ojdbc, you are using oracle's driver
oracle.jdbc.driver.OracleDriver
for this, you need to have classes12.jar
Filip
aku1234 wrote:
I double checked everything. There is an ojdbc.jar file in TC_HOME/lib
and nowhere else.
I'm not sure that it even knows what
I'm sorry, I must have confused you. After we dowloaded ojdbc14.jar from
Oracle we just
renamed it to ojdbc.jar. I believe this is for use with JDK 1.4 and above.
I think the
classes12.jar is for JDK 1.2 and 1.3. For the record we're using the latest
version of Java 5.
I opened up
got it,
you could turn on debugging for DBCP and JNDI, by adding
org.apache.naming.level=FINE
org.apache.tomcat.dbcp.level=FINE
to the bottom of your TC_HOME/conf/logging.properties
that might give you a clue, somehow your entered JNDI names don't match
with what Tomcat think it has bound
12 matches
Mail list logo
