hmmm, interesting.... I'm using driver $CATALINA_HOME/lib/mysql-connector-java-5.1.5-bin.jar In my resource name declarations in my server.xml I'm using: driverClassName="com.mysql.jdbc.Driver which I have already verified is in that jar. Why would tomcat be referencing a different jdbc driver even though I'm correctly referencing the mysql driver? thanks -dustin
________________________________ From: Propes, Barry L [mailto:[EMAIL PROTECTED] Sent: Tue 3/18/2008 5:28 PM To: Tomcat Users List Subject: RE: jndi resource linking >>>I have the mysql driver in lib, I dont believe that is the issue. I kind of do...I was about to ask if you were using or referencing the correct driver. I don't think you'd be getting this error if that was the case. >>>>Cannot create JDBC driver of class ' ' or connect URL 'null' >>>>java.lang.NullPointerException >>>>at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(JdbcOdbcDriver.java:507) >>>>It feels like the linking process between the context and the global >>>>resource isnt happening because the stack trace is complaining of a null >>>>pointer. Are we sure this reference is the correct driver? It very well may be, but I don't think it should reference that sun driver mentioned there with using JNDI. driverClassName="com.mysql.jdbc.Driver" It's been a while since I used mysql and granted I didn't take it down the JNDI road. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
