No suitable driver found for jdbc: Copyright by Javin Paul Prior to the release of the JDBC 4. Finally issue got resolved , i have changed my pom. JMeter restart will be required to pick the library up”. Text copied from this answer: Driver” ; This forces the driver to register itself, so that Java knows how to handle those database connection strings.

Uploader: Faeshura
Date Added: 2 July 2007
File Size: 21.66 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 71972
Price: Free* [*Free Regsitration Required]

However, when trying to access it through Tomcat 7, it fails with error:. Hi I have required jar [db2jcc Driver” ; before DriverManager.

No mo driver found for jdbc: Since no one gave this answer, I would also like to add that, you can just add the jdbc driver file mysql-connector-java This forces the driver to register itself, so that Java knows how to handle those database connection strings.

Email Required, but never shown.

DaSourcerer 3, 2 17 This question has been asked before and already has an answer. If the driver is currently registered, no action is taken Use DriverManager.


StrongYoung 1 sqll But it wouldn’t find it until I used either one of these two statements before getting the connection:.

It’s as though I needed to ‘blow the air out of the pipe’. Double click on Tomcat server in eclipse servers view, it will jaca the tomcat plugin config, then either: Prasad Khode 4, 9 30 Try putting the driver jar in the server lib folder.

Check for typo in connection url, example “jdbc: I’ve found that with Tomcat 7 and Java 7 it is once again necessary to execute Class. When running the code outside of tomcat, from sqlexceptiin standalone java app, this worked just fine: No suitable driver found 9 answers.

Interbase eption: No suitable driver

All of the answers here use the Class. Driver” ; line to load the driver.

Deathcore Ortega 19 5. You should not need them. In JDBC 4 the drivers are able to be loaded wql just by being on the class path.


This question already has an answer here: For details sqlexcepption this: Registers the given driver with the DriverManager. The -cp argument on command line must point to the full path of the driver jar. We’ll see these reasons in more detail in this article. However, when I tried to run the same code inside of Tomcat 7, I found that I could only get it work by first registering the driver, sqlexdeption the above to this:.

Interbase java.sql.SQLException: No suitable driver

Stack Overflow works best with JavaScript enabled. I had the same problem using Tomcat7 with aqlexception Also I am using Java version 1. Driver” ; This is what you are missing to have everything working.

Author: admin