You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/04/10 18:41:10 UTC
DO NOT REPLY [Bug 15672] -
DBCP doesn't work on Tomcat 4.1.18 with Oracle JDBC driver
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15672>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15672
DBCP doesn't work on Tomcat 4.1.18 with Oracle JDBC driver
------- Additional Comments From alan@coldsmoke.com 2003-04-10 16:41 -------
I had the same issue. What fixed my problem was that I had to change
the "path" and "docBase" of the context from "/TestDB" and "TestDB" (the ones
on the man page) to be the context I was using the pool from (in my
case, "irongrid"). Once I did that, everything worked great.
A search on google shows that the "driver is 'null'" issue is fairly
common. Maybe the solution is just to update the JDNI-HowTo at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-
howto.html
to explicitly mention this problem. Something like, "If you encounter 'cannot
load null driver', then make sure that you context is set to blah blah blah."
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org