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
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.
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
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
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 driver it's trying to load.
The top part of the stacktrace was:
Cannot create JDBC
My code works on Tomcat 5.5.25, but when I move it to
Tomcat 6.0.14 it stops working. When it starts up
it succefully loads Acegi(Spring) which is using JNDI.
Then when it tries to load Hibernate which uses the
same JNDI resource, it doesn't work. Hibernate and JNDI
work just fine on Tomcat
