- #Java no suitable driver found for drivers#
- #Java no suitable driver found for driver#
- #Java no suitable driver found for registration#
I will open a PR for option 2 as I don't believe there is a strong need to remain DB agnostic here unless anyone believes otherwise. Replace DriverManager with an OracleDataSource.Retrieve and set-up an instance of the directly same as Liquibase, not going through the DriverManager.
#Java no suitable driver found for driver#
The DriverManager.getConnection(.) loop continues and exhausts with no valid driver found, and subsequently raises the 'No suitable driver found for url.' exception.The DriverManager validates whether the Class returned from the utPLSQL Maven Plugin classloader matches the previously registered driver - they do not as the registered one is an instance living in the Liquibase Plugin classloader and evaluates the permission check to false Try avoiding the usage of Class.forName() as there might be some quirks for the classloading.
#Java no suitable driver found for registration#
runs its static initialisation logic, attempts to register itself with the DriverManager - however as registration is addIfAbsent in DriverManager.registerDriver(.) the Liquibase registered one remains.The DriverManager attempts to fetch from the current utPLSQL Maven Plugin classloader, it does not yet exist so it provides a fresh one.
#Java no suitable driver found for drivers#
The DriverManager sets up and starts looping through the registered drivers (containing the instance of the OracleDriver registered by the Liquibase plugin previously), it then validates whether the caller has permission to load the driver or not using isDriverAllowed(Driver driver, ClassLoader classLoader) Trying to create jdbc source connector (confluent 5.1) and getting errors " No suitable driver." but I do have the connector jar.The utPLSQL Maven Plugin starts up and hits DriverManager.getConnection(.).As part of static initialisation in the it registers itself with the DriverManager.Liquibase as part of its run loads the into a child classloader it uses in DatabaseFactory.getConnection(.).Maven spins up a Classloader for the Liquibase Maven Plugin (see )( ).I had the chance to debug a bit further today so as to understand the root cause for the Liquibase + utPLSQL combination issue. I know we can't package ojdbc due to - the utplsql-api is published to It's more or less the same information.We have java-api packaged with maven plugin? That way, users don't need to pull needed package manually into their private (enterprise) repo. Or what's the point of setting ATL_DB_TYPE and ATL_DB_DRIVER. perhaps you should pair this string with the choice of ATL_DB_TYPE. Now i need a coffee or my head will explode.Įdit: Jira has no entry of _class even though ATL_DB_TYPE is set.
Create the needed database (jboss) and the needed username and password.14 posts Post the complete log details.
The postgresql-container is in the same network 17:49:43,886 ERROR setupDatabase Unable to connect to database: : No suitable driver found for confluence_db 17:49:43,884 ERROR getTestDatabaseConnection Could not successfully test your database: 09:01:04,804 ERROR setupDatabase Unable to connect to database: : No suitable driver found for confluence_db 09:01:04,788 ERROR getTestDatabaseConnection Could not successfully test your database: 19:11:06,377 ERROR setupDatabase Unable to connect to database: : No suitable driver found for confluence_db The errors: 19:11:06,373 ERROR getTestDatabaseConnection Could not successfully test your database: