java.sql.SQLException: No suitable driver

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843830, 1 year ago
[IBM][JDBC Driver] CLI0627E The result set is not scrollable.
via Oracle Community by 843859, 1 year ago
[IBM][JDBC Driver] CLI0627E The result set is not scrollable. 6900690 SystemErr R
via Google Groups by Tom, 2 years ago
[IBM][JDBC Driver] CLI0626E La fonction getXAConnection() through the net driver n'est pas prise en charge par la présente version du pilote DB2 JDBC 2.0.
via Oracle Community by 843859, 5 months ago
[Microsoft][SQLServer 2000 Driver for JDBC]The specified SQL type is not supported by this driver.
via Google Groups by Harry Chou, 5 months ago
[Microsoft][SQLServer JDBC Driver] [SQLServer]Login failed for user 'lcg'.
via Oracle Community by 3004, 1 year ago
java.sql.SQLException: No suitable driver
at java.lang.Throwable.(Throwable.java)
at java.lang.Throwable.(Throwable.java)
at java.sql.SQLException.(SQLException.java:72)
at java.sql.DriverManager.getDriver(DriverManager.java:266)
at com.solarmetric.jdbc.PoolingDataSource.getDriver(PoolingDataSource.java:271)
at com.solarmetric.jdbc.PoolingDataSource.newConnection(PoolingDataSource.java:313)
at com.solarmetric.jdbc.ConnectionPoolImpl.makeObject(ConnectionPoolImpl.java:230)
at com.solarmetric.jdbc.ConnectionPoolImpl.getConnection(ConnectionPoolImpl.java:163)
at com.solarmetric.jdbc.PoolingDataSource.getConnection(PoolingDataSource.java:237)
at com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:128)
at kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:251)
at kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:56)
at kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:568)
at kodo.jdbc.schema.DataSourceFactory.configureDataSource(DataSourceFactory.java:119)
at kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:799)
at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:882)
at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:891)
at kodo.jdbc.schema.SchemaTool.(SchemaTool.java:67)
at kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:243)
at kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:233)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:856)
at kodo.jdbc.integration.eclipse.MappingToolAction.doFile(MappingToolAction.java:90)
at kodo.jdbc.integration.eclipse.MappingToolAction.handleFile(MappingToolAction.java:61)
at kodo.jdbc.integration.eclipse.AbstractMetadataAction.run(AbstractMetadataAction.java:62)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.AccessibleObject.invokeL(AccessibleObject.java:207)
at java.lang.reflect.Method.invoke(Method.java:271)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.