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 2002/01/16 15:39:19 UTC
DO NOT REPLY [Bug 5881] New: -
DB2 JDBC: no suitable 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=5881>.
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=5881
DB2 JDBC: no suitable driver!
Summary: DB2 JDBC: no suitable driver!
Product: Tomcat 4
Version: 4.0.1 Final
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Blocker
Priority: Other
Component: Webapps
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: ralf.eichinger@rbg.de
though including the db2java.zip (renamed to db2java.jar) in the WEB-INF/lib
directory of my webapp jdbc does not work anymore. it worked under tomcat 3.2.3!
the error message is: java.sql.Exception: No suitable driver in
java.sql.DriverManager.getConnection( line 537 ).
i've tried several approaches:
- unpack zip and put classes in WEB-INF/classes
- put jars in common/lib, /lib, WEB-INF/lib
- unpack db2java.zip and repack with jar
no approach works.
a test-jdbc-application with the same db2java.zip-package in the classpath
works!
what went wrong from tomcat 3.2.3 to 4?
i've found several people in newsgroups having exact the same problem!
HELP!
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>