RE: No Suitable Driver Problem
Please double check and make sure your ojdbc.jar is in $CATALINA_HOME/common/lib. -Original Message- From: MARU, SOHIL (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 8:02 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Problem Hey Doug, I tried moving the username up, still does not work, any other clues, am still stumped. Thanks, Sohil Server.xml Context path=/loa docBase=C:\software\eclipse\workspace\HRTechnology\TOMCAT_ROOT reloadable=true Resource name=jdbc/loacenet auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/loacenet . . . . parameter namepassword/name valuedatabasepassword/value /parameter parameter nameurl/name valuejdbc:oracle:[EMAIL PROTECTED]:1521:[sid]/value /parameter parameter namedriverClassName/name valueoracle.jdbc.driver.OracleDriver/value /parameter parameter nameusername/name valueuser/value /parameter /ResourceParams /Context However when I try to load my plugin in the struts application, I get the following exception. I looked at everything on archives and on there people were complaining about NULL for driverClassName, in my case, it reads the drivername and url properly and still blows up. Please help. I am using Tomcat 5.0 with the latest ojdbc14.jar/commons-dbcp-1.1.jar in common/lib and am trying to connect to oracle 8.1.7. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class ' oracle.jdbc.driver.OracleDriver' for connect URL 'jdbc:oracle:[EMAIL PROTECTED] :1521:[sid]', cause: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:243) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:743) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:518) at com.sbc.hrtech.framework.utility.InitializerPlugin.init(InitializerPl ugin.java:41) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle t.java:1158) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:473) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper. java:1044) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:88 7) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex t.java:3960) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 283) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardHost.start(StandardHost.java:832) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518 ) at org.apache.catalina.core.StandardService.start(StandardService.java:5 19) at org.apache.catalina.core.StandardServer.start(StandardServer.java:234 5) at org.apache.catalina.startup.Catalina.start(Catalina.java:598) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) Excpetion in InitializerPlugin The java code in the plugin is as follows Context init = new InitialContext(); Context ctx = (Context) init.lookup(java:comp/env); DataSource dataSource = (DataSource) ctx.lookup(jdbc/loacenet); c = dataSource.getConnection(); -- line which blows up st = c.createStatement(); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
RE: No Suitable Driver Problem
Hi Daniel, I managed to solve this one, my database url was missing the schema name, that was causing the problem. I changed it from jdbc:oracle:[EMAIL PROTECTED] To jdbc:oracle:thin:[EMAIL PROTECTED] But it is still throwing an exception though a different one. Any pointers? java.lang.NullPointerException at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnecti on.java:195) at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec tion.java:129) at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola bleConnectionFactory.java:311) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(Bas icDataSource.java:842) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:821) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:518) at com.sbc.hrtech.framework.utility.InitializerPlugin.init(InitializerPl ugin.java:41) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle t.java:1158) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:473) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper. java:1044) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:88 7) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex t.java:3960) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 283) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardHost.start(StandardHost.java:832) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518 ) at org.apache.catalina.core.StandardService.start(StandardService.java:5 19) at org.apache.catalina.core.StandardServer.start(StandardServer.java:234 5) at org.apache.catalina.startup.Catalina.start(Catalina.java:598) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) Excpetion in InitializerPlugin -Original Message- From: Daniel Huang [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 11:22 AM To: Tomcat Users List Subject: RE: No Suitable Driver Problem Please double check and make sure your ojdbc.jar is in $CATALINA_HOME/common/lib. -Original Message- From: MARU, SOHIL (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 8:02 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Problem Hey Doug, I tried moving the username up, still does not work, any other clues, am still stumped. Thanks, Sohil Server.xml Context path=/loa docBase=C:\software\eclipse\workspace\HRTechnology\TOMCAT_ROOT reloadable=true Resource name=jdbc/loacenet auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/loacenet . . . . parameter namepassword/name valuedatabasepassword/value /parameter parameter nameurl/name valuejdbc:oracle:[EMAIL PROTECTED]:1521:[sid]/value /parameter parameter namedriverClassName/name valueoracle.jdbc.driver.OracleDriver/value /parameter parameter nameusername/name valueuser/value /parameter /ResourceParams /Context However when I try to load my plugin in the struts application, I get the following exception. I looked at everything on archives and on there people were complaining about NULL for driverClassName, in my case, it reads the drivername and url properly and still blows up. Please help. I am using Tomcat 5.0 with the latest ojdbc14.jar/commons-dbcp-1.1
RE: No Suitable Driver Problem
Never mind, even though I am using jdk1.4 and tomcat5.0, I had to replace ojdbc14.jar with classes version to get it to work. -Original Message- From: MARU, SOHIL (SBCSI) Sent: Friday, April 09, 2004 11:26 AM To: 'Tomcat Users List' Subject: RE: No Suitable Driver Problem Hi Daniel, I managed to solve this one, my database url was missing the schema name, that was causing the problem. I changed it from jdbc:oracle:[EMAIL PROTECTED] To jdbc:oracle:thin:[EMAIL PROTECTED] But it is still throwing an exception though a different one. Any pointers? java.lang.NullPointerException at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnecti on.java:195) at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec tion.java:129) at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola bleConnectionFactory.java:311) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(Bas icDataSource.java:842) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:821) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:518) at com.sbc.hrtech.framework.utility.InitializerPlugin.init(InitializerPl ugin.java:41) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle t.java:1158) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:473) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper. java:1044) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:88 7) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex t.java:3960) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 283) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardHost.start(StandardHost.java:832) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518 ) at org.apache.catalina.core.StandardService.start(StandardService.java:5 19) at org.apache.catalina.core.StandardServer.start(StandardServer.java:234 5) at org.apache.catalina.startup.Catalina.start(Catalina.java:598) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) Excpetion in InitializerPlugin -Original Message- From: Daniel Huang [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 11:22 AM To: Tomcat Users List Subject: RE: No Suitable Driver Problem Please double check and make sure your ojdbc.jar is in $CATALINA_HOME/common/lib. -Original Message- From: MARU, SOHIL (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 8:02 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Problem Hey Doug, I tried moving the username up, still does not work, any other clues, am still stumped. Thanks, Sohil Server.xml Context path=/loa docBase=C:\software\eclipse\workspace\HRTechnology\TOMCAT_ROOT reloadable=true Resource name=jdbc/loacenet auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/loacenet . . . . parameter namepassword/name valuedatabasepassword/value /parameter parameter nameurl/name valuejdbc:oracle:[EMAIL PROTECTED]:1521:[sid]/value /parameter parameter namedriverClassName/name valueoracle.jdbc.driver.OracleDriver/value /parameter parameter nameusername/name valueuser/value /parameter /ResourceParams /Context However when I try to load my plugin in the struts application, I
Re: No Suitable Driver Problem
Sohil, At what line in your code is it blowing up? As a follow up, once you have it all fixed would try the username back at the bottom to see if it breaks it again? I'm running MySQL so I didn't spot the error, sorry. Doug - Original Message - From: MARU, SOHIL (SBCSI) [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, April 09, 2004 12:25 PM Subject: RE: No Suitable Driver Problem Hi Daniel, I managed to solve this one, my database url was missing the schema name, that was causing the problem. I changed it from jdbc:oracle:[EMAIL PROTECTED] To jdbc:oracle:thin:[EMAIL PROTECTED] But it is still throwing an exception though a different one. Any pointers? java.lang.NullPointerException at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnecti on.java:195) at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec tion.java:129) at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola bleConnectionFactory.java:311) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(Bas icDataSource.java:842) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:821) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:518) at com.sbc.hrtech.framework.utility.InitializerPlugin.init(InitializerPl ugin.java:41) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle t.java:1158) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:473) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper. java:1044) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:88 7) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex t.java:3960) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 283) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardHost.start(StandardHost.java:832) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518 ) at org.apache.catalina.core.StandardService.start(StandardService.java:5 19) at org.apache.catalina.core.StandardServer.start(StandardServer.java:234 5) at org.apache.catalina.startup.Catalina.start(Catalina.java:598) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) Excpetion in InitializerPlugin -Original Message- From: Daniel Huang [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 11:22 AM To: Tomcat Users List Subject: RE: No Suitable Driver Problem Please double check and make sure your ojdbc.jar is in $CATALINA_HOME/common/lib. -Original Message- From: MARU, SOHIL (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 8:02 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Problem Hey Doug, I tried moving the username up, still does not work, any other clues, am still stumped. Thanks, Sohil Server.xml Context path=/loa docBase=C:\software\eclipse\workspace\HRTechnology\TOMCAT_ROOT reloadable=true Resource name=jdbc/loacenet auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/loacenet . . . . parameter namepassword/name valuedatabasepassword/value /parameter parameter nameurl/name valuejdbc:oracle:[EMAIL PROTECTED]:1521:[sid]/value /parameter parameter namedriverClassName/name valueoracle.jdbc.driver.OracleDriver/value /parameter parameter nameusername/name valueuser/value /parameter
Re: No suitable driver
Success! Thanks for your help Doug. I am going to submit this to the developer list to be added to the Tomcat docs. The winning configuration for MS SQLServer is as follows: server.xml: !-- 'type' is not javax.sql.DataSource as it ordinarily would be -- Resource name=jdbc/dbName auth=Container type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource/ ResourceParams name=jdbc/dbName parameter namefactory/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory/value /parameter parameter namemaxActive/name value100/value /parameter !-- serverName is required by the MS driver -- parameter nameserverName/name valuelocalhost/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\databaseName/value /parameter !-- Oddly, user and password cannot be appended to the URL -- parameter nameuser/name valueusername/value /parameter parameter namepassword/name valuepassword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams In the Context element in webappname.xml: ResourceLink name=jdbc/dbName global=jdbc/dbName type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource / In the web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name !-- Luckily this can remain javax.sql.DataSource so the war is portable -- res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, Should have known that MS would do something screwy with their setup. Check out this page from the archives. http://archives.real-time.com/pipermail/tomcat-users/2002-December/088536.html Notice also that the type is set to a different name and yes they do have the factory in there. Give it a try and let us know. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, March 27, 2004 6:39 PM Subject: Re: No suitable driver Doug, I made those changes and I still have the same problem. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://localhost\dbname;user=username;password=password ', cause: No suitable driver Here's my config info: From server.xml: GlobalNamingResources Resource name=jdbc/dbName auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/dbName parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\dbName;user=username;password=pa ssword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME/conf/Catalina/localhost/webappname.xml: Context path=/webappname docBase=webappname debug=5 reloadable=true crossContext=true ResourceLink name=jdbc/dbName global=jdbc/dbName type=javax.sql.DataSource / /Context From web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The code: Context context = new InitialContext(); DataSource dataSource = (DataSource)context.lookup(java:comp/env/jdbc/dbName); return dataSource.getConnection(); Also, this is Tomcat 5.0.16 on Win2k. And as for: parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter this was straight out of the Tomcat docs, but removing it doesn't seem to make a difference. Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, This: Resource name=resourceName auth=Container
Re: No suitable driver
Todd, One correction to your notes (I think). The web.xml type should also change. Unless you have tested it otherwise, the reason it works is that Tomcat is not using the resource info from the web.xml when it's in the server.xml . You can confirm this by removing it. But otherwise I'm glad you got it working. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, March 29, 2004 8:12 PM Subject: Re: No suitable driver Success! Thanks for your help Doug. I am going to submit this to the developer list to be added to the Tomcat docs. The winning configuration for MS SQLServer is as follows: server.xml: !-- 'type' is not javax.sql.DataSource as it ordinarily would be -- Resource name=jdbc/dbName auth=Container type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource/ ResourceParams name=jdbc/dbName parameter namefactory/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory/value /parameter parameter namemaxActive/name value100/value /parameter !-- serverName is required by the MS driver -- parameter nameserverName/name valuelocalhost/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\databaseName/value /parameter !-- Oddly, user and password cannot be appended to the URL -- parameter nameuser/name valueusername/value /parameter parameter namepassword/name valuepassword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams In the Context element in webappname.xml: ResourceLink name=jdbc/dbName global=jdbc/dbName type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource / In the web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name !-- Luckily this can remain javax.sql.DataSource so the war is portable -- res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, Should have known that MS would do something screwy with their setup. Check out this page from the archives. http://archives.real-time.com/pipermail/tomcat-users/2002-December/088536.html Notice also that the type is set to a different name and yes they do have the factory in there. Give it a try and let us know. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, March 27, 2004 6:39 PM Subject: Re: No suitable driver Doug, I made those changes and I still have the same problem. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://localhost\dbname;user=username;password=password ', cause: No suitable driver Here's my config info: From server.xml: GlobalNamingResources Resource name=jdbc/dbName auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/dbName parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\dbName;user=username;password=pa ssword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME/conf/Catalina/localhost/webappname.xml: Context path=/webappname docBase=webappname debug=5 reloadable=true crossContext=true ResourceLink name=jdbc/dbName global=jdbc/dbName type=javax.sql.DataSource / /Context From web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The code
Re: No suitable driver
That is exactly how my web.xml is. I tested it and it works. I even removed it like you just suggested and that worked too. As long as long as Tomcat is ignoring it, I'll keep it that way so the war remains portable. I am only using SQLServer for prototyping. I do not plan to stick with it long-term. Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, One correction to your notes (I think). The web.xml type should also change. Unless you have tested it otherwise, the reason it works is that Tomcat is not using the resource info from the web.xml when it's in the server.xml . You can confirm this by removing it. But otherwise I'm glad you got it working. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, March 29, 2004 8:12 PM Subject: Re: No suitable driver Success! Thanks for your help Doug. I am going to submit this to the developer list to be added to the Tomcat docs. The winning configuration for MS SQLServer is as follows: server.xml: !-- 'type' is not javax.sql.DataSource as it ordinarily would be -- Resource name=jdbc/dbName auth=Container type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource/ ResourceParams name=jdbc/dbName parameter namefactory/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory/value /parameter parameter namemaxActive/name value100/value /parameter !-- serverName is required by the MS driver -- parameter nameserverName/name valuelocalhost/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\databaseName/value /parameter !-- Oddly, user and password cannot be appended to the URL -- parameter nameuser/name valueusername/value /parameter parameter namepassword/name valuepassword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams In the Context element in webappname.xml: ResourceLink name=jdbc/dbName global=jdbc/dbName type=com.microsoft.jdbcx.sqlserver.SQLServerDataSource / In the web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name !-- Luckily this can remain javax.sql.DataSource so the war is portable -- res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, Should have known that MS would do something screwy with their setup. Check out this page from the archives. http://archives.real-time.com/pipermail/tomcat-users/2002-December/088536.html Notice also that the type is set to a different name and yes they do have the factory in there. Give it a try and let us know. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, March 27, 2004 6:39 PM Subject: Re: No suitable driver Doug, I made those changes and I still have the same problem. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://localhost\dbname;user=username;password=password ', cause: No suitable driver Here's my config info: From server.xml: GlobalNamingResources Resource name=jdbc/dbName auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/dbName parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\dbName;user=username;password=pa ssword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME
Re: No suitable driver
Doug, I made those changes and I still have the same problem. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://localhost\dbname;user=username;password=password', cause: No suitable driver Here's my config info: From server.xml: GlobalNamingResources Resource name=jdbc/dbName auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/dbName parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\dbName;user=username;password=password/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME/conf/Catalina/localhost/webappname.xml: Context path=/webappname docBase=webappname debug=5 reloadable=true crossContext=true ResourceLink name=jdbc/dbName global=jdbc/dbName type=javax.sql.DataSource / /Context From web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The code: Context context = new InitialContext(); DataSource dataSource = (DataSource)context.lookup(java:comp/env/jdbc/dbName); return dataSource.getConnection(); Also, this is Tomcat 5.0.16 on Win2k. And as for: parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter this was straight out of the Tomcat docs, but removing it doesn't seem to make a difference. Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, This: Resource name=resourceName auth=Container type=javax.sql.DataSource/ This: ResourceParams name=resourceName This: ResourceLink name=jdbc/dbname global=resourceName type=javax.sql.DataSource / This: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbname/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref And this after java:/comp/env/: (DataSource)initContext.lookup(java:/comp/env/jdbc/*DbName*); Set all to have the same name as well as global.. (It's easier) parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter Mine does not use this. I am not a 100% on this but I don't think this is neccesary or legit to have it here. IE just remove or comment it out until you get things workin. parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://hostname/value /parameter parameter nameDatabaseName/name valuedbname/value /parameter Most people put this as part of the URL. I am pretty sure that this is ok but the name should be databaseName. parameter nameUser/name valueusername/value /parameter Set User to user. parameter namePassword/name valuepassword/value /parameter Set Password to password. is all I see at the moment. Doug PS yes I know that you can set the names different, but it can cause more headaches than its worth if you don't have it just right.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No suitable driver
Todd, Should have known that MS would do something screwy with their setup. Check out this page from the archives. http://archives.real-time.com/pipermail/tomcat-users/2002-December/088536.html Notice also that the type is set to a different name and yes they do have the factory in there. Give it a try and let us know. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, March 27, 2004 6:39 PM Subject: Re: No suitable driver Doug, I made those changes and I still have the same problem. org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://localhost\dbname;user=username;password=password ', cause: No suitable driver Here's my config info: From server.xml: GlobalNamingResources Resource name=jdbc/dbName auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/dbName parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost\dbName;user=username;password=pa ssword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME/conf/Catalina/localhost/webappname.xml: Context path=/webappname docBase=webappname debug=5 reloadable=true crossContext=true ResourceLink name=jdbc/dbName global=jdbc/dbName type=javax.sql.DataSource / /Context From web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbName/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The code: Context context = new InitialContext(); DataSource dataSource = (DataSource)context.lookup(java:comp/env/jdbc/dbName); return dataSource.getConnection(); Also, this is Tomcat 5.0.16 on Win2k. And as for: parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter this was straight out of the Tomcat docs, but removing it doesn't seem to make a difference. Thanks again, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, This: Resource name=resourceName auth=Container type=javax.sql.DataSource/ This: ResourceParams name=resourceName This: ResourceLink name=jdbc/dbname global=resourceName type=javax.sql.DataSource / This: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbname/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref And this after java:/comp/env/: (DataSource)initContext.lookup(java:/comp/env/jdbc/*DbName*); Set all to have the same name as well as global.. (It's easier) parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter Mine does not use this. I am not a 100% on this but I don't think this is neccesary or legit to have it here. IE just remove or comment it out until you get things workin. parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://hostname/value /parameter parameter nameDatabaseName/name valuedbname/value /parameter Most people put this as part of the URL. I am pretty sure that this is ok but the name should be databaseName. parameter nameUser/name valueusername/value /parameter Set User to user. parameter namePassword/name valuepassword/value /parameter Set Password to password. is all I see at the moment
Re: No suitable driver
Doug, Yes, I am using TC5, the drivers work when I connect directly via DriverManager and are in common/lib. Here are the relevant parts of my server.xml: GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource Resource name=resourceName auth=Container type=javax.sql.DataSource/ ResourceParams name=resourceName parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://hostname/value /parameter parameter nameDatabaseName/name valuedbname/value /parameter parameter nameUser/name valueusername/value /parameter parameter namePassword/name valuepassword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbcx.sqlserver.SQLServerDataSource/value /parameter /ResourceParams ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources From $TOMCAT_HOME/conf/Catalina/localhost/webappname.xml: Context path=/webappname docBase=webappname debug=5 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_webappname_log. suffix=.txt timestamp=true/ ResourceLink name=jdbc/dbname global=resourceName type=javax.sql.DataSource / /Context And from web.xml: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbname/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The code snippet is below, in the original email. Thank you, Todd --- Parsons Technical Services [EMAIL PROTECTED] wrote: Todd, I assume you are running TC5? Please post your configs from the server.xml, web.xml, context.xml and code snippet you use to get a connection. Because you are getting a driver it is at least seeing some of your config. Are you using the correct drivers? Are they current? Are they corrupted? Driver jar goes in common/lib. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 10:12 PM Subject: No suitable driver All, I know that this issue has been posted many times, I have read many of them and and the Tomcat docs but to no avail... The names between the '*'s have been sanitized. The following code: Context initContext = new InitialContext(); DataSource ds = (DataSource)initContext.lookup(java:/comp/env/jdbc/*DbName*); Connection conn = ds.getConnection(); produces the following results: java.lang.Exception: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://*hostname*', cause: No suitable driver In the interest of keeping this brief I won't include all of the config, but I've tried putting the Resource ResourceParams definitions in the Context element for the webapp in server.xml. I've also put the Resource ResourceParams definitions in the GlobalNamingResources in the server.xml with a ResourceLink in the Context element in $CATALINA_HOME/*webapp*.xml. I've also tried this with a context.xml in the META-INF directory of the webapp. The jars for the driver are in common\lib, but I've also tried putting them in every other imaginable lib directory too. I would greatly appreciate any help. Thank you, Todd __ Do you Yahoo!? Yahoo!
Re: No suitable driver
Todd, This: Resource name=resourceName auth=Container type=javax.sql.DataSource/ This: ResourceParams name=resourceName This: ResourceLink name=jdbc/dbname global=resourceName type=javax.sql.DataSource / This: resource-ref descriptionDB Connection/description res-ref-namejdbc/dbname/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref And this after java:/comp/env/: (DataSource)initContext.lookup(java:/comp/env/jdbc/*DbName*); Set all to have the same name as well as global.. (It's easier) parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter Mine does not use this. I am not a 100% on this but I don't think this is neccesary or legit to have it here. IE just remove or comment it out until you get things workin. parameter namemaxActive/name value100/value /parameter parameter namemaxIdle/name value30/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://hostname/value /parameter parameter nameDatabaseName/name valuedbname/value /parameter Most people put this as part of the URL. I am pretty sure that this is ok but the name should be databaseName. parameter nameUser/name valueusername/value /parameter Set User to user. parameter namePassword/name valuepassword/value /parameter Set Password to password. is all I see at the moment. Doug PS yes I know that you can set the names different, but it can cause more headaches than its worth if you don't have it just right.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No suitable driver
Todd, I assume you are running TC5? Please post your configs from the server.xml, web.xml, context.xml and code snippet you use to get a connection. Because you are getting a driver it is at least seeing some of your config. Are you using the correct drivers? Are they current? Are they corrupted? Driver jar goes in common/lib. Doug - Original Message - From: Todd H. Siegel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 10:12 PM Subject: No suitable driver All, I know that this issue has been posted many times, I have read many of them and and the Tomcat docs but to no avail... The names between the '*'s have been sanitized. The following code: Context initContext = new InitialContext(); DataSource ds = (DataSource)initContext.lookup(java:/comp/env/jdbc/*DbName*); Connection conn = ds.getConnection(); produces the following results: java.lang.Exception: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.microsoft.jdbcx.sqlserver.SQLServerDataSource' for connect URL 'jdbc:microsoft:sqlserver://*hostname*', cause: No suitable driver In the interest of keeping this brief I won't include all of the config, but I've tried putting the Resource ResourceParams definitions in the Context element for the webapp in server.xml. I've also put the Resource ResourceParams definitions in the GlobalNamingResources in the server.xml with a ResourceLink in the Context element in $CATALINA_HOME/*webapp*.xml. I've also tried this with a context.xml in the META-INF directory of the webapp. The jars for the driver are in common\lib, but I've also tried putting them in every other imaginable lib directory too. I would greatly appreciate any help. Thank you, Todd __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No Suitable Driver Error -- Still No Success
What does your web.xml look like? Read step 3 on this page: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples -howto.html -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 9:46 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Error -- Still No Success Importance: High Hi , I am getting the following error in JDBC connection pooling. Error log and other details are as follows: Please help !! Regards Abhay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No Suitable Driver Error -- Still No Success
Having just gone through a similar issue last week, I can recommend searching the archives (and maybe the bug database). You'll probably find your solution. If you're getting this error when you start up Tomcat, then it's probably fixable (you may have a JAR in the wrong place, etc.) If you're getting this error after doing a hot redeploy, then you may not get it to work TC4. At least, that's the conclusion I've reached. Note that two responses to my issue said that their problems went away with TC5, but after making the switch yesterday, I still don't have Tomcat re-recognizing the resource after a hot redeploy. I'm still working on it... Jay -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 9:46 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Error -- Still No Success Importance: High Hi , I am getting the following error in JDBC connection pooling. Error log and other details are as follows: Please help !! Regards Abhay - I am using :== Apache Tomcat/4.1.29 SQL*Plus: Release 9.0.1.4.0 - Production on Mon Feb 2 09:39:33 2004 Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production j2sdk1.4.2_03 ojdbc14.jar ---ERROR - Feb 3, 2004 9:36:40 AM org.apache.struts.util.PropertyMessageResources init INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true Looking up jdbc/estimation Found Feb 3, 2004 9:36:52 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 80 Feb 3, 2004 9:36:53 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Feb 3, 2004 9:36:53 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=40/270 config=C:\Tomcat\bin\..\conf\jk2.properties 2004-02-03 09:37:29,921 [http80-Processor4] DEBUG (class com.mot.iDEN.webapp.oes.tags.GetCurrListTag ) - GetCurrListTag.doStartTag() 2004-02-03 09:37:29,941 [http80-Processor4] DEBUG (class com.mot.iDEN.webapp.oes.tags.GetCurrListTag ) - GetCurrListTag.getTestData() 2004-02-03 09:37:30,081 [http80-Processor4] DEBUG (class com.mot.iDEN.webapp.oes.factory.AdminFactor y) - AdminFactory.getTestData() **1** **2** **3** Caught while creating a connection in EPP dB:=org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null', cause: No suitable driver 2004-02-03 09:37:30,161 [http80-Processor4] ERROR (class com.mot.iDEN.webapp.oes.factory.AdminFactor y) - AdminFactory.getTestData java.lang.NullPointerException at com.mot.iDEN.webapp.oes.config.EstimationConfigurator.getEstimationConne ction(EstimationC onfigurator.java:193) at com.mot.iDEN.webapp.oes.factory.AdminFactory.getTestData(AdminFactory.ja va:3492) at com.mot.iDEN.webapp.oes.tags.GetCurrListTag.getTestData(GetCurrListTag.j ava:1268) at com.mot.iDEN.webapp.oes.tags.GetCurrListTag.doStartTag(GetCurrListTag.ja va:745) at org.apache.jsp.oes_db_test_jsp._jspService(oes_db_test_jsp.java:73) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.j ava:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(Standar dPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(Standar dPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 7) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(Standar dPipeline.java:643)
RE: No Suitable Driver Error -- Still No Success
This is my Web.xml resource-ref res-ref-namejdbc/estimation/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Abhay -Original Message- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 10:03 AM To: 'Tomcat Users List' Subject: RE: No Suitable Driver Error -- Still No Success What does your web.xml look like? Read step 3 on this page: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples -howto.html -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 9:46 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Error -- Still No Success Importance: High Hi , I am getting the following error in JDBC connection pooling. Error log and other details are as follows: Please help !! Regards Abhay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No Suitable Driver Error -- Still No Success
It's been a while since I did Oracle jdbc urls... jdbc:oracle:thin:@oswego.comm.mot.com:1521:remedydb is remedydb your sid? how about your schema? I'm thinking there's something missing between :thin: and the @ symbol. But it might not always be required... ? -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 10:11 AM To: 'Tomcat Users List' Subject: RE: No Suitable Driver Error -- Still No Success Importance: High This is my Web.xml resource-ref res-ref-namejdbc/estimation/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Abhay -Original Message- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 10:03 AM To: 'Tomcat Users List' Subject: RE: No Suitable Driver Error -- Still No Success What does your web.xml look like? Read step 3 on this page: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasourc e-examples -howto.html -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 9:46 AM To: [EMAIL PROTECTED] Subject: No Suitable Driver Error -- Still No Success Importance: High Hi , I am getting the following error in JDBC connection pooling. Error log and other details are as follows: Please help !! Regards Abhay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No Suitable Driver Error -- Still No Success
Hi , I am getting the following error in JDBC connection pooling. Error log and other details are as follows: Please help !! Regards Abhay Caught while creating a connection in EPP dB:=org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null', cause: No suitable driver Hi Abhay, here I had the same problem some time ago. I can't reproduce exactly how we solved the problem, but we solved it ;-) Here's a Context from my server.xml: Context path=/idp className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=9 displayName=displayName docBase=C:/java/tomcat4.1.29/webapps/idp mapperClass=org.apache.catalina.core.StandardContextMapper privileged=false reloadable=false swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper Resource auth=Container name=jdbc/idp scope=Shareable type=javax.sql.DataSource/ ResourceParams name=jdbc/idp parameter namemaxWait/name value5000/value /parameter parameter namemaxActive/name value40/value /parameter parameter namepassword/name value/value /parameter parameter nameurl/name valuejdbc:postgresql://127.0.0.1/idp/value /parameter parameter namedriverClassName/name valueorg.postgresql.Driver/value /parameter parameter namemaxIdle/name value2/value /parameter parameter nameusername/name valuestnt1/value /parameter /ResourceParams /Context and here's the according resource-ref from the web.xml: resource-ref res-ref-namejdbc/idp/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref The postgresql.jar with the driver class resides in $CATALINA_HOME/common/lib . Good luck, B. Burkhart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No suitable driver
I had a problem somewhat simular to that.
Make sure you have access to the driver in the bean class.
Maybe a required library or something.
Tim
-Original Message-
From: Meichun Li [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 12:01 PM
To: Tomcat Users List
Subject: No suitable driver
Hi, I am suing Oreilly books wrapper class for connection pool. It works
fine in the servlet class while I created a datasource using
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
But it doesn't work in the javabean class using the same code:
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
No problem while compiling. But there is run time error: No suitable
driver.
I print the stack error in the end of the message.
There should be no problem in the classpath setting. I tried to find the
driver in the javabean class and the driver can be found. Related codes:
try
{
Class.forName(org.gjt.mm.mysql.Driver);
}
catch ( ClassNotFoundException coe)
{
System.err.println(Class not found + coe.getMessage());
}
Why it is working in servlet but not in javabean ? I've searched the
archive but couldn't find helpful information.
Any help are greatly appreciated!
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:543)
at java.sql.DriverManager.getConnection(DriverManager.java:183)
at org.ibiblio.sql.ConnectionPool.init(ConnectionPool.java:38)
at
org.ibiblio.sql.DataSourceWrapper.init(DataSourceWrapper.java:21)
at
org.ibiblio.osprey.DataSourceBean.getMaxID(DataSourceBean.java:34)
at org.ibiblio.osprey.TestDataSource.main(TestDataSource.java:16)
Regards,
Meichun
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: No suitable driver
have you tried:
Class.forName(org.gjt.mm.mysql.Driver).newInstance();
Si
-Original Message-
From: The Kelley's [mailto:[EMAIL PROTECTED]]
Sent: 17 July 2002 17:17
To: Tomcat Users List
Subject: RE: No suitable driver
I had a problem somewhat simular to that.
Make sure you have access to the driver in the bean class.
Maybe a required library or something.
Tim
-Original Message-
From: Meichun Li [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 12:01 PM
To: Tomcat Users List
Subject: No suitable driver
Hi, I am suing Oreilly books wrapper class for connection pool. It works
fine in the servlet class while I created a datasource using
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
But it doesn't work in the javabean class using the same code:
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
No problem while compiling. But there is run time error: No suitable
driver.
I print the stack error in the end of the message.
There should be no problem in the classpath setting. I tried to find the
driver in the javabean class and the driver can be found. Related codes:
try
{
Class.forName(org.gjt.mm.mysql.Driver);
}
catch ( ClassNotFoundException coe)
{
System.err.println(Class not found + coe.getMessage());
}
Why it is working in servlet but not in javabean ? I've searched the
archive but couldn't find helpful information.
Any help are greatly appreciated!
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:543)
at java.sql.DriverManager.getConnection(DriverManager.java:183)
at org.ibiblio.sql.ConnectionPool.init(ConnectionPool.java:38)
at
org.ibiblio.sql.DataSourceWrapper.init(DataSourceWrapper.java:21)
at
org.ibiblio.osprey.DataSourceBean.getMaxID(DataSourceBean.java:34)
at org.ibiblio.osprey.TestDataSource.main(TestDataSource.java:16)
Regards,
Meichun
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: No suitable driver
On Wed, 17 Jul 2002, The Kelley's wrote:
I had a problem somewhat simular to that.
Make sure you have access to the driver in the bean class.
Maybe a required library or something.
Tim
Thanks for the reply. Could you explain more detail about the access to
the driver?
In my bean class, if using the standard JDBC connection instead of using
the datasource, there is no probelm. Is this mean that my bean class could
access to the driver?
Thanks,
Meichun
-Original Message-
From: Meichun Li [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 12:01 PM
To: Tomcat Users List
Subject: No suitable driver
Hi, I am suing Oreilly books wrapper class for connection pool. It works
fine in the servlet class while I created a datasource using
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
But it doesn't work in the javabean class using the same code:
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
No problem while compiling. But there is run time error: No suitable
driver.
I print the stack error in the end of the message.
There should be no problem in the classpath setting. I tried to find the
driver in the javabean class and the driver can be found. Related codes:
try
{
Class.forName(org.gjt.mm.mysql.Driver);
}
catch ( ClassNotFoundException coe)
{
System.err.println(Class not found + coe.getMessage());
}
Why it is working in servlet but not in javabean ? I've searched the
archive but couldn't find helpful information.
Any help are greatly appreciated!
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:543)
at java.sql.DriverManager.getConnection(DriverManager.java:183)
at org.ibiblio.sql.ConnectionPool.init(ConnectionPool.java:38)
at
org.ibiblio.sql.DataSourceWrapper.init(DataSourceWrapper.java:21)
at
org.ibiblio.osprey.DataSourceBean.getMaxID(DataSourceBean.java:34)
at org.ibiblio.osprey.TestDataSource.main(TestDataSource.java:16)
Regards,
Meichun
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: No suitable driver
That's what it sounds like. For some reason your bean class can't see the
driver.
Tim
-Original Message-
From: Meichun Li [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 12:20 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: No suitable driver
On Wed, 17 Jul 2002, The Kelley's wrote:
I had a problem somewhat simular to that.
Make sure you have access to the driver in the bean class.
Maybe a required library or something.
Tim
Thanks for the reply. Could you explain more detail about the access to
the driver?
In my bean class, if using the standard JDBC connection instead of using
the datasource, there is no probelm. Is this mean that my bean class could
access to the driver?
Thanks,
Meichun
-Original Message-
From: Meichun Li [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 12:01 PM
To: Tomcat Users List
Subject: No suitable driver
Hi, I am suing Oreilly books wrapper class for connection pool. It works
fine in the servlet class while I created a datasource using
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
But it doesn't work in the javabean class using the same code:
ds = new DataSourceWrapper(jdbcDriverClassName, jdbcURL, dbUserName,
dbUserPassword);
No problem while compiling. But there is run time error: No suitable
driver.
I print the stack error in the end of the message.
There should be no problem in the classpath setting. I tried to find the
driver in the javabean class and the driver can be found. Related codes:
try
{
Class.forName(org.gjt.mm.mysql.Driver);
}
catch ( ClassNotFoundException coe)
{
System.err.println(Class not found + coe.getMessage());
}
Why it is working in servlet but not in javabean ? I've searched the
archive but couldn't find helpful information.
Any help are greatly appreciated!
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:543)
at java.sql.DriverManager.getConnection(DriverManager.java:183)
at org.ibiblio.sql.ConnectionPool.init(ConnectionPool.java:38)
at
org.ibiblio.sql.DataSourceWrapper.init(DataSourceWrapper.java:21)
at
org.ibiblio.osprey.DataSourceBean.getMaxID(DataSourceBean.java:34)
at org.ibiblio.osprey.TestDataSource.main(TestDataSource.java:16)
Regards,
Meichun
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
Meichun Li
Ibiblio.org
919-962-5646
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: not suitable driver?
Hi Isak, the DriverManager has a method called availableDriver or so. Use this to show, if your driver is registered. If yes, your driver could be registered, but can not do his work with the database. This is no problem of Tomcat. If no, the driver.jar was not found by tomcat. Then try Class.forName(org.gjt.mm.mysql.Driver).getInstance(); If this doesn't help, look to your context. Do you have a own context for your webapplication. Create one and put the driver.jar to WEB-INF/lib. Anja -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: not suitable driver?
getConnection(jdbc:mysql:3306://localhost/bukujsp?snip Surely you mean: getConnection(jdbc:mysql//localhost:3306/bukujsp?snip They may be identical. Anyone? J. -- You're only jealous cos the little penguins are talking to me. *** For more information on Ordnance Survey products and services, visit our web site at http://www.ordnancesurvey.co.uk *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: No suitable driver Datasource Problem
I'm would guess that your JDBC driver is not available to the correct class loader. Try moving the JDBC driver up to the TOMCAT_HOME/lib/common directory, restart Tomcat, and see if that works. Randy -Original Message- From: remy.menetrieux [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 7:51 AM To: Tomcat Users List Subject: No suitable driver Datasource Problem When I use a datasource I obtain this error. But when i use same option directly in my servelt all is OK. Have you seen this errors ??? regards Remy Java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:249) at tyrex.jdbc.xa.EnabledDataSource.getConnection(EnabledDataSourc e.java:233) at tyrex.jdbc.xa.EnabledDataSource.getConnection(EnabledDataSourc e.java:204) at fr.pixelpark.erh.servlets.ApplicantServlet.performTask(Applica ntServlet.java :92) at fr.pixelpark.toolbox.servlets.PixelServlet.doGet(PixelServlet. java:33) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilt er(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli cationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardW rapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardC ontextValve.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(Certificat esValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardContext.invoke(StandardContex t.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHost Valve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi spatcherValve. java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport Valve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValv e.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEn gineValve.java :174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpP rocessor.java: 1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProce ssor.java:1107 ) at java.lang.Thread.run(Thread.java:484) Le code : Context initCtx = new InitialContext(); Context envCtx = (Context) initCtx.lookup( java:comp/env ); // Look up our data source out.println(envCtx =+envCtx); DataSource ds = envCtx.lookup(jdbc/ErhDB); -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: No suitable driver Datasource Problem
Thanks it's work... Remy Randy Layman wrote: I'm would guess that your JDBC driver is not available to the correct class loader. Try moving the JDBC driver up to the TOMCAT_HOME/lib/common directory, restart Tomcat, and see if that works. Randy -Original Message- From: remy.menetrieux [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 7:51 AM To: Tomcat Users List Subject: No suitable driver Datasource Problem When I use a datasource I obtain this error. But when i use same option directly in my servelt all is OK. Have you seen this errors ??? regards Remy Java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:249) at tyrex.jdbc.xa.EnabledDataSource.getConnection(EnabledDataSourc e.java:233) at tyrex.jdbc.xa.EnabledDataSource.getConnection(EnabledDataSourc e.java:204) at fr.pixelpark.erh.servlets.ApplicantServlet.performTask(Applica ntServlet.java :92) at fr.pixelpark.toolbox.servlets.PixelServlet.doGet(PixelServlet. java:33) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilt er(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli cationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardW rapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardC ontextValve.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(Certificat esValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardContext.invoke(StandardContex t.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHost Valve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi spatcherValve. java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport Valve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValv e.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEn gineValve.java :174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardP ipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja va:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpP rocessor.java: 1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProce ssor.java:1107 ) at java.lang.Thread.run(Thread.java:484) Le code : Context initCtx = new InitialContext(); Context envCtx = (Context) initCtx.lookup( java:comp/env ); // Look up our data source out.println(envCtx =+envCtx); DataSource ds = envCtx.lookup(jdbc/ErhDB); -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: No suitable driver
Option 1: Search the mailing list archives and discover that this is an EXTREMELY common question. The benefit of this is that you don't have to put up with people like me telling you to go look at a place you should have thought to look before you sent your question. Option 2: Rename your .zip file to .jar. Then place the file in your WEB-INF/lib folder. If you are trying to use JDBCRealm (which you aren't, but I'll say it for everyone else reading the message) then the .jar file will need to go into either TOMCAT_HOME/lib or the classpath. Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 01, 2001 12:28 PM To: [EMAIL PROTECTED] Subject: No suitable driver Hi! Thank you, Cory. I've got another problem after enclosing the variables in quotes: ---//- Internal Servlet Error: javax.servlet.ServletException: No suitable driver at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCont extImpl.java:459) ---//--- How must I install JDBC drivers? My configuration: CLASSPATH=/u01/app/oracle/product/8.0.5/jdbc/lib/classes111.zip - This mail was sent through Eoffice: http://www.eoffice.dk
Re: No suitable driver
String url = jdbc:pool:oracle:thin:@localhost:1521:MY_DB; Since you are using thin oracle client driver, I think the pool should not be there. In my work place, I use only this connection URL string. String url = jdbc:oracle:thin:@host:port:sid - Hari. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 01, 2001 9:57 PM Subject: No suitable driver Hi! Thank you, Cory. I've got another problem after enclosing the variables in quotes: ---//- Internal Servlet Error: javax.servlet.ServletException: No suitable driver at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCont extImpl.java:459) ---//--- How must I install JDBC drivers? My configuration: CLASSPATH=/u01/app/oracle/product/8.0.5/jdbc/lib/classes111.zip - This mail was sent through Eoffice: http://www.eoffice.dk
