-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hakari Pool - Failed to initialize pool: ConnectionStringHostListProvider does not support identifyConnection #1314
Comments
Hi @aleruz-dt Thank you for reaching out with this issue. Could you please provide driver logs? This will help troubleshoot the issue. For reference: https://github.com/aws/aws-advanced-jdbc-wrapper/blob/main/docs/using-the-jdbc-driver/UsingTheJdbcDriver.md#logging Also, to clarify, are you only seeing this issue with the 2.5.5 driver and Hikari 6.2.1? e.g., Does Wrapper 2.5.4 work correctly with Hikari 6.2.1? From what I can see from the provided exception, the driver hasn't identified the database dialect properly. As a quick remedy for the issue, I can suggest to add an additional configuration parameter |
I am also seeing this issue using Dropwizard + Hibernate and an underlying Tomcat pool, so it seems not limited to only Hikari. I can confirm that 2.5.4 works, and 2.5.5 does not work. Setting the wrapperDialect also does not fix the problem. Attaching trace level logs.
|
Same issue from standalone DB migration app, using local Postgres (testcontainer).
|
@sergiyvamz worked with exact same configuration with 2.5.4, broke when renovate bot updated the version. |
Looking at the call chain, I guess it's this change to blame: 85e1b3c#diff-6a324c434d1b42882f5bd3191705a27875305f4adedac858cc98a0bf15277c6fR96-R99 It causes a call to |
Describe the bug
While upgrading the library from 2.5.4 to 2.5.5, I got the following error:
com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: ConnectionStringHostListProvider does not support identifyConnection
Hikari is in the latest version https://mvnrepository.com/artifact/com.zaxxer/HikariCP/6.2.1
Expected Behavior
The driver works as before with Hikari.
What plugins are used? What other connection properties were set?
default settings
Current Behavior
java.lang.UnsupportedOperationException: ConnectionStringHostListProvider does not support identifyConnection. at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.hostlistprovider.ConnectionStringHostListProvider.identifyConnection(ConnectionStringHostListProvider.java:119) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.PluginServiceImpl.identifyConnection(PluginServiceImpl.java:723) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.PluginServiceImpl.fillAliases(PluginServiceImpl.java:752) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.plugin.AuroraConnectionTrackerPlugin.connect(AuroraConnectionTrackerPlugin.java:101) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.lambda$connect$6(ConnectionPluginManager.java:390) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.lambda$null$3(ConnectionPluginManager.java:278) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.executeWithTelemetry(ConnectionPluginManager.java:246) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.lambda$makePluginChainFunc$4(ConnectionPluginManager.java:277) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.executeWithSubscribedPlugins(ConnectionPluginManager.java:236) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ConnectionPluginManager.connect(ConnectionPluginManager.java:387) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.wrapper.ConnectionWrapper.init(ConnectionWrapper.java:161) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.wrapper.ConnectionWrapper.<init>(ConnectionWrapper.java:105) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ds.AwsWrapperDataSource.createConnectionWrapper(AwsWrapperDataSource.java:255) at aws.advanced.jdbc.wrapper@2.5.5/software.amazon.jdbc.ds.AwsWrapperDataSource.getConnection(AwsWrapperDataSource.java:210) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:367) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:205) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:484) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:572) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:101) at com.zaxxer.hikari@6.2.1/com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:111)
Reproduction Steps
DataSourceClassname: software.amazon.jdbc.ds.AwsWrapperDataSource
DataSourceProperties: targetDataSourceClassName:org.postgresql.ds.PGSimpleDataSource
Possible Solution
No response
Additional Information/Context
No response
The AWS Advanced JDBC Driver version used
2.5.5
JDK version used
openjdk version "21.0.2" 2024-01-16 LTS OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode)
Operating System and version
mac / linux
The text was updated successfully, but these errors were encountered: