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
com.kumuluz.ee.testing
kumuluzee-arquillian-container
1.0.0
test
org.jboss.arquillian.junit
arquillian-junit-container
1.4.0.Final
test
Exception we get
Exception in thread "main" java.lang.RuntimeException: Failed to load class of driverClassName [org.postgresql.Driver] in either of HikariConfig class loader or Thread context classloader
at com.zaxxer.hikari.HikariConfig.setDriverClassName(HikariConfig.java:334)
at com.kumuluz.ee.EeApplication.initialize(EeApplication.java:262)
at com.kumuluz.ee.EeApplication.(EeApplication.java:73)
at com.kumuluz.ee.testing.arquillian.assets.MainWrapper.main(MainWrapper.java:44)
And looks like it is an issue with Hikari dependency.
We tried using the suggested version by excluding and including the one which they said has fixed the issue but still get the same exception.
Any suggestions ?
The text was updated successfully, but these errors were encountered:
It seems like the Postgres driver is missing in the deployment. I assume you are using the MavenDependencyAppender mechanism to add dependencies to the deployment.
Can you check if the Postgres driver is missing in the appender?
We are having issues injecting datasources using
com.kumuluz.ee.testing
kumuluzee-arquillian-container
1.0.0
test
org.jboss.arquillian.junit
arquillian-junit-container
1.4.0.Final
test
Exception we get
Exception in thread "main" java.lang.RuntimeException: Failed to load class of driverClassName [org.postgresql.Driver] in either of HikariConfig class loader or Thread context classloader
at com.zaxxer.hikari.HikariConfig.setDriverClassName(HikariConfig.java:334)
at com.kumuluz.ee.EeApplication.initialize(EeApplication.java:262)
at com.kumuluz.ee.EeApplication.(EeApplication.java:73)
at com.kumuluz.ee.testing.arquillian.assets.MainWrapper.main(MainWrapper.java:44)
Some research pointed us to -
brettwooldridge/HikariCP#982
And looks like it is an issue with Hikari dependency.
We tried using the suggested version by excluding and including the one which they said has fixed the issue but still get the same exception.
Any suggestions ?
The text was updated successfully, but these errors were encountered: