RE: No suitable driver exception after upgrade - Pedro Nevado - com.mysql.lists.java

7 messages in com.mysql.lists.javaRE: No suitable driver exception afte...

From	Sent On	Attachments
Steve Kirk	19 May 2005 12:28
Mark Matthews	19 May 2005 12:38
Steve Kirk	19 May 2005 12:43
Pedro Nevado	19 May 2005 12:51
Hollerman Geralyn M	19 May 2005 13:18
Pedro Nevado	19 May 2005 14:38
Steve Kirk	20 May 2005 07:28

Subject:	RE: No suitable driver exception after upgrade
From:	Pedro Nevado (pnev...@javato.com)
Date:	05/19/2005 02:38:04 PM
List:	com.mysql.lists.java

Steve, in case it helps, this is my datasource configuration in ROOT.xml. Also, I do not put my jdbc driver or my connection pool jars in common/lib, but in the .war file (WEB-INF/lib) of my web application.

<Resource name="jdbc/madridDS" auth="Container" type="com.mchange.v2.c3p0.ComboPooledDataSource"/> <ResourceParams name="jdbc/madridDS"> <parameter> <name>factory</name> <value>org.apache.naming.factory.BeanFactory</value> </parameter>  <parameter> <name>maxActive</name> <value>100</value> </parameter>  <parameter> <name>maxIdle</name> <value>30</value> </parameter>  <parameter> <name>maxWait</name> <value>5000</value> </parameter>  <parameter> <name>username</name> <value>me</value> </parameter> <parameter> <name>password</name> <value>me</value> </parameter>  <parameter> <name>driverClassName</name> <value>com.mysql.jdbc.Driver</value> </parameter>  <parameter> <name>url</name> <value>

jdbc:mysql://localhost:3306/finmadrid?autoReconnect=true</value> </parameter> <parameter> <name>removeAbandoned</name> <value>true</value> </parameter> <parameter> <name>removeAbandonedTimeout</name> <value>120</value> </parameter> <parameter> <name>logAbandoned</name> <value>true</value> </parameter> </ResourceParams>

And this is the part in web.xml:  <resource-ref> <description>DataSource para acceder a BD finmadrid en mysql. </description> <res-ref-name>jdbc/madridDS</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> <res-sharing-scope>Shareable</res-sharing-scope> </resource-ref>

-----Mensaje original----- De: Steve Kirk [mailto:sjk-...@web-startup.co.uk] Enviado el: jueves, 19 de mayo de 2005 22:10 Para: 'Pedro Nevado' Asunto: RE: No suitable driver exception after upgrade

Thanks Pedro. I've tried 3.1.8 too, no joy.

A bit more info that might help: The connection pool initially seems to work, in the sense that this code executes OK: Context ctx = new InitialContext(); String resourceString = "java:comp/env/jdbc/" + config.getString(ConfigConstants.JNDI_DATABASE_RESOURCE_NAME); DataSource pool = (DataSource)ctx.lookup(resourceString);

The Exception is only thrown when I later do this: Connection conn = pool.getConnection();

Does that suggest a particular problem to anyone?

-----Original Message----- From: Pedro Nevado [mailto:pnev...@javato.com] Sent: Thursday 19 May 2005 20:52 To: mysql_java Subject: RE: No suitable driver exception after upgrade

Hi, I did exactly the same upgrade than you, without any problems. The only differences in my architecture is that I use c3Po as connection pool, the connector/j 3.1.8 version and Windows 2000 (Server, Pro); with those ones, I have not experienced any problem.

As to the configuration of Tomcat 5.5.9, the biggest difference I have found so far is related to the context.xml related wiht the root application; but they do not affect, I think, your data base access.

-----Mensaje original----- De: Steve Kirk [mailto:sjk-...@web-startup.co.uk] Enviado el: jueves, 19 de mayo de 2005 21:29 Para: ja...@lists.mysql.com Asunto: No suitable driver exception after upgrade

Hi,

I'm posting here because I'm not sure if I am dealing with a mysql or a tomcat issue. I'm hoping that someone else has seen the same issue before.

Until recently I had a working webapp running on tomcat 5.0.28 with connector/j 3.1.7 and mysql 4.1.11-nt, all on windows xp and jdk1.4.2_08. The app uses the commons DBCP for all its database access. The DBCP resource config has been set up and working unchanged for a long time. I have it set up like this:

<ResourceParams> defined in context.xml, in war file's META-INF folder <resource-ref> declared in web.xml in war file's WEB-INF folder The connector/j jar file is in tomcat's /common/lib folder name of JNDI resource matches in <ResourceParams>, <resource-ref> and Java source code.

So far so good. However, I am attempting to upgrade to JDK1.5 and TC 5.5.9. I did a fresh install of both of these to standard directories, recompiled the webapp for jdk1.5, and deployed it with the same config files and setup above from TC 5.0.28. However the webapp now reports an error on startup, see stacktrace below.

I'm stumped after hours working on this. I've read through all the docs, how-tos, and release notes that I can find, and searched the mail list archives on mysql and tomcat sites, as well as googling various searches. Has anyone had this problem themselves or have any insight to offer please?

Thanks,

----------------------------------------------------------------- Exception caught when establishing/testing database pool**** cause[0]: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(B asicDataSource .java:780) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(Basi cDataSource.ja va:540) at core.sql.SqlQuery.prepare(SqlQuery.java:80) at core.sql.SqlQuery.executeSingleValue(SqlQuery.java:133) at core.servlet.Invoker.setUpDataSource(Invoker.java:325) at core.servlet.Invoker.init(Invoker.java:129) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardW rapper.java:10 91) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper. java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(Standar dContext.java: 3857) at org.apache.catalina.core.StandardContext.start(StandardContext .java:4118) at org.apache.catalina.core.ContainerBase.addChildInternal(Contai nerBase.java:7 59) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase. java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostCo nfig.java:589) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostC onfig.java:536 ) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:471) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConf ig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L ifecycleSuppor t.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService .java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:683) at org.apache.catalina.startup.Catalina.start(Catalina.java:537) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409) cause[1]: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:243) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(B asicDataSource .java:773) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(Basi cDataSource.ja va:540) at core.sql.SqlQuery.prepare(SqlQuery.java:80) at core.sql.SqlQuery.executeSingleValue(SqlQuery.java:133) at core.servlet.Invoker.setUpDataSource(Invoker.java:325) at core.servlet.Invoker.init(Invoker.java:129) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardW rapper.java:10 91) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper. java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(Standar dContext.java: 3857) at org.apache.catalina.core.StandardContext.start(StandardContext .java:4118) at org.apache.catalina.core.ContainerBase.addChildInternal(Contai nerBase.java:7 59) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase. java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostCo nfig.java:589) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostC onfig.java:536 ) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:471) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConf ig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L ifecycleSuppor t.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService .java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:683) at org.apache.catalina.startup.Catalina.start(Catalina.java:537) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)

tup.co.uk