NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central · #660 by repository stars
Ultimate JDBC Connection Pool
Last release 9 years ago
no release in 18 months
Ships fairly regularly
a new release about every 4 months
Nearly every release is documented
notes for 6 of 6 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
6 releases · first in 2016
backport more efficient contention handling in ConcurrentBag.requite from 2.6.x branch.
backport more efficient contention handling in ConcurrentBag.requite from 2.6.x branch.
issue 955 fix possible race condition when Statements are closed on different threads from which they were created.
issue 878 search for driverClass in both HikariCP class classloader and Thread Context ClassLoader
One column per quarter.
issue 793 add new HikariConfig method, setScheduledExecutor(ScheduledExecutorService), and deprecate method setScheduledExecutorService(ScheduledThrea…
issue 793 add new HikariConfig method, setScheduledExecutor(ScheduledExecutorService), and deprecate method setScheduledExecutorService(ScheduledThreadPoolExecutor). It is unfortunate that the deprecated method has the more accurate name, but its signature cannot be changed without breaking binary compatibility.
issue 600 ignore Java 8 default methods when generating proxy classes for Java 7.
issue 770 add a new property initializationFailTimeout, and deprecate configuration property initializationFailFast.
Redesign of the contention code path resulting in doubling contended throughput; now contended pool access retains 98% of the uncontended throughput.
issue 770 add a new property initializationFailTimeout, and deprecate configuration property initializationFailFast.
issue 774 significantly improve spike load handling.
issue 741 cancel HouseKeeper task on pool shutdown. If the ScheduledExecutor being used did not belong to HikariCP, this task would remain scheduled after shutdown, causing a memory leak.
issue 719 only reset lastConnectionFailure after a successful dataSource.getConnection() call.
issue 719 only reset lastConnectionFailure after a successful dataSource.getConnection() call.
issue 716 do not scan deeper than 10 nested SQLExceptions, it's typically a trap ... a chain that never terminates.
issue 714 fix possible issue with cross-thread visibility. Change pool entry state from AtomicInteger w/lazySet() to a volatile int with use of AtomicIntegerFieldUpdater.
Release 2.4.8 marks the start of a Java 7 HikariCP artifact, HikariCP-java7, representing support for Java 7 entering maintenance mode.
Release 2.4.8 marks the start of a Java 7 HikariCP artifact, HikariCP-java7, representing support for Java 7 entering maintenance mode.
Added Connection.commit() call to the fail-fast initialization for databases that automatically start a new Connection in a transaction and throw an exception on close if it is not committed.
feature 694: report if a previously reported leaked connection is returned to the pool
issue 689: log a warning if default transaction isolation level cannot be detected. This can occur with pseudo-database drivers such as the one for JSonar
issue 674: fix regression caused by pull request #450 (overzealous optimisation)
Your coding agent can read these notes before it upgrades. Set up the MCP server →