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 Google Groups by Torche Guillaume, 1 year ago
java.sql. SQLException: No suitable driver found for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
via GitHub by grocon
, 1 year ago
java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/xxxxxxx
via Google Groups by prinull, 11 months ago
java.sql. SQLException: Cannot create PoolableConnectionFactory (java.net. ConnectException : Error connecting to server localhost on port 1,527 with message Connection refused.)
via GitHub by drcrallen
, 2 years ago
java.sql.SQLException: Cannot create JDBC driver of class 'org.apache.derby.jdbc.ClientDriver' for connect URL 'jdbc:derby:memory:druidTest95a2ba02711d4cff92eb4505d254ec72'
via Google Groups by Julien Heiduk, 10 months ago
java.sql.SQLException: Cannot create PoolableConnectionFactory (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.)
org.skife.jdbi.v2.exceptions.UnableToObtainConnectionException: java.sql.SQLException: No suitable driver found for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX at org.skife.jdbi.v2.DBI.open(DBI.java:210)[jdbi-2.32.jar:?] at org.skife.jdbi.v2.DBI.withHandle(DBI.java:257)[jdbi-2.32.jar:?] at io.druid.server.namespace.JDBCExtractionNamespaceFunctionFactory$3.call(JDBCExtractionNamespaceFunctionFactory.java:105)[druid-namespace-lookup-0.8.1.jar:0.8.1] at io.druid.server.namespace.JDBCExtractionNamespaceFunctionFactory$3.call(JDBCExtractionNamespaceFunctionFactory.java:96)[druid-namespace-lookup-0.8.1.jar:0.8.1] at io.druid.server.namespace.cache.NamespaceExtractionCacheManager$5.run(NamespaceExtractionCacheManager.java:356)[druid-namespace-lookup-0.8.1.jar:0.8.1] at com.google.common.util.concurrent.MoreExecutors$ScheduledListeningDecorator$NeverSuccessfulListenableFutureTask.run(MoreExecutors.java:582)[guava-16.0.1.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[?:1.8.0_45] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[?:1.8.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[?:1.8.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[?:1.8.0_45] at java.lang.Thread.run(Thread.java:745)[?:1.8.0_45]Caused by: java.sql.SQLException: No suitable driver found for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX at java.sql.DriverManager.getConnection(DriverManager.java:689)[?:1.8.0_45] at java.sql.DriverManager.getConnection(DriverManager.java:247)[?:1.8.0_45] at org.skife.jdbi.v2.DBI$3.openConnection(DBI.java:136)[jdbi-2.32.jar:?] at org.skife.jdbi.v2.DBI.open(DBI.java:192)[jdbi-2.32.jar:?] ... 12 more