github aws/aws-advanced-jdbc-wrapper 4.7.0
AWS Advanced JDBC Wrapper - v4.7.0

one hour ago

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[4.7.0] - 2026-11-19

🪄 Added

  • Added the Host Monitoring Plugin v3 (efm3), which registers each connection with its host monitor once instead of on every JDBC call, so per-call overhead no longer takes shared locks or allocates and monitor memory scales with the number of connections rather than with call volume. In the wrapper's benchmarks, which use a simulated target driver with many connections to one host, efm3 handled about 2.7 times as many calls per millisecond as efm2 at 8 or more threads (685-737 versus 246-268), and with 64 connections making 1,000 calls per second each it held 5-6 MB of heap instead of about 125 MB. efm and efm2 are unchanged, and efm2 remains the default (PR #2237, documentation).
  • Added the Connection Lifetime Plugin (connectionLifetime), which limits how long a physical connection is used through connectionLifetimeMs, and either reconnects through the endpoint originally supplied by the application or closes the connection when it expires, deferring the action until an active transaction ends (PR #2228, documentation).
  • Added eviction of expired and aborted connections from the internal HikariCP connection pool, so a connection closed by the Connection Lifetime Plugin or aborted by Enhanced Failure Monitoring is not handed out again (PR #2257, documentation).

🐛 Fixed

  • Fixed connections through RDS Proxy failing after the first connection because the Aurora PostgreSQL dialect sent connection metadata as startup options, which RDS Proxy rejects. Connection metadata is no longer sent to RDS Proxy endpoints, and the new enableConnectionMetadata property controls it explicitly (Issue #2240, PR #2252, documentation).
  • Fixed the Blue/Green Deployment Plugin staying in the POST phase indefinitely after a completed switchover, which also caused it to ignore the deletion and recreation of the deployment (PR #2242, documentation).
  • Fixed a class configured through targetDataSourceClassName being initialized and instantiated before the wrapper verified that it is a DataSource; the type is now checked before any of the class's code runs (PR #2235).

🦀 Changed

  • Replaced ordered dialect probing with fingerprint-based detection. The wrapper now runs one to three error-free catalog statements on the first connection instead of up to seven, and the detected dialect no longer depends on the endpoint type, which fixes Global Aurora MySQL clusters reached through an instance endpoint, RDS Proxy or a custom domain resolving to the Aurora MySQL dialect. Dialect.isDialect and Dialect.getDialectUpdateCandidates are deprecated (PR #2238, documentation).
  • The current transaction state is now read from the target driver when it reports one (PostgreSQL JDBC, MySQL Connector/J and MariaDB Connector/J), and is inferred from executed SQL only when the driver cannot report it. On MySQL with autocommit=false, a statement that does not start a server-side transaction, such as SELECT 1, is no longer treated as opening one, so failover in that case raises FailoverSuccessSQLException instead of TransactionStateUnknownSQLException (PR #2215, documentation).
  • Dependency updates, including AWS SDK 2.59.1, Jackson Databind 2.23.0 and 3.3.0, Jackson JSR-310 2.23.0, OpenTelemetry 1.68.0, Hibernate ORM 7.4.15.Final, jsoup 1.24.1, Vert.x 4.5.36, Gradle wrapper 8.14.7, and GitHub Actions updates (PR #2223, PR #2224, PR #2225, PR #2226, PR #2227, PR #2229, PR #2246, PR #2247, PR #2248, PR #2249, PR #2250).
  • Documentation: documented HikariCP and c3p0 compatibility across Java runtimes and updated the configuration assistant to recommend compatible pool versions (PR #2219, documentation).

Don't miss a new aws-advanced-jdbc-wrapper release

NewReleases is sending notifications on new releases.