You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing some unit tests which fork off peons or testing, and they are now failing due to the following:
2015-12-23T14:23:38,758 WARN [main] com.metamx.common.RetryUtils - Failed on try 3, retrying in 10,760ms.
org.skife.jdbi.v2.exceptions.UnableToObtainConnectionException: java.sql.SQLException: Cannot create JDBC driver of class 'org.apache.derby.jdbc.ClientDriver' for connect URL 'jdbc:derby:memory:druidTest95a2ba02711d4cff92eb4505d254ec72'
at org.skife.jdbi.v2.DBI.open(DBI.java:230) ~[jdbi-2.63.1.jar:2.63.1]
at org.skife.jdbi.v2.DBI.withHandle(DBI.java:279) ~[jdbi-2.63.1.jar:2.63.1]
at io.druid.metadata.SQLMetadataConnector$2.call(SQLMetadataConnector.java:110) ~[classes/:?]
at com.metamx.common.RetryUtils.retry(RetryUtils.java:38) [java-util-0.27.5.jar:?]
at io.druid.metadata.SQLMetadataConnector.retryWithHandle(SQLMetadataConnector.java:115) [classes/:?]
at io.druid.metadata.SQLMetadataConnector.createTable(SQLMetadataConnector.java:160) [classes/:?]
at io.druid.metadata.SQLMetadataConnector.createConfigTable(SQLMetadataConnector.java:258) [classes/:?]
at io.druid.metadata.SQLMetadataConnector.createConfigTable(SQLMetadataConnector.java:410) [classes/:?]
at io.druid.guice.JacksonConfigManagerModule$1.start(JacksonConfigManagerModule.java:58) [classes/:?]
at com.metamx.common.lifecycle.Lifecycle.start(Lifecycle.java:259) [java-util-0.27.5.jar:?]
at io.druid.guice.LifecycleModule$2.start(LifecycleModule.java:155) [druid-api-0.3.15.jar:?]
at io.druid.cli.GuiceRunnable.initLifecycle(GuiceRunnable.java:73) [classes/:?]
at io.druid.cli.CliPeon.run(CliPeon.java:151) [classes/:?]
at io.druid.cli.Main.main(Main.java:101) [classes/:?]
Caused by: java.sql.SQLException: Cannot create JDBC driver of class 'org.apache.derby.jdbc.ClientDriver' for connect URL 'jdbc:derby:memory:druidTest95a2ba02711d4cff92eb4505d254ec72'
at org.apache.commons.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:2023) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:1897) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1413) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.skife.jdbi.v2.DataSourceConnectionFactory.openConnection(DataSourceConnectionFactory.java:36) ~[jdbi-2.63.1.jar:2.63.1]
at org.skife.jdbi.v2.DBI.open(DBI.java:212) ~[jdbi-2.63.1.jar:2.63.1]
... 13 more
Caused by: java.sql.SQLException: No suitable driver
at org.apache.commons.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:2014) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:1897) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1413) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.skife.jdbi.v2.DataSourceConnectionFactory.openConnection(DataSourceConnectionFactory.java:36) ~[jdbi-2.63.1.jar:2.63.1]
at org.skife.jdbi.v2.DBI.open(DBI.java:212) ~[jdbi-2.63.1.jar:2.63.1]
... 13 more
Derby should be OK for unit tests. This is using the TestDerbyConnector.DerbyConnectorRule which creates an in-memory db
The text was updated successfully, but these errors were encountered:
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
I'm writing some unit tests which fork off peons or testing, and they are now failing due to the following:
Derby should be OK for unit tests. This is using the
TestDerbyConnector.DerbyConnectorRule
which creates an in-memory dbThe text was updated successfully, but these errors were encountered: