diff options
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 88 |
1 files changed, 87 insertions, 1 deletions
@@ -1,13 +1,71 @@ HikariCP Changes +Changes in 2.7.1 + + * issue 968 Wrong label order in MicrometerMetricsTracker for the connection usage + metric. + + * issue 967 incorrect bitwise operator value in ConcurrentBag.requite method + intended to cause parkNanos() to be called every 256 iterations. Thanks to @ztkmkoo + for finding this. + +Changes in 2.7.0 + + * added support for micrometer metrics (currently Alpha-level support). + + * issue 905 mask JDBC password in URLs + + * issue 940 fix Prometheus metric collector for multiple data config + + * issue 941 add support for setting a default schema + + * issue 955 fix possible race condition when Statements are closed on different + threads from which they were created. + +Changes in 2.6.3 + + * issue 878 load driver class from ThreadContext classloader if it is not found + via the regular classloader. + +Changes in 2.6.2 + + * issue 890 add support for Prometheus metrics and multiple HikariCP pools. + + * issue 880 fix race condition caused by sorting collection while the condition of + sort can change. + + * issue 876 add support for using a Prometheus CollectorRegistry other than the + default one. + + * issue 867 support network timeout even for Connection.isValid(). + + * issue 866 mark commit state dirty when Connection.getMetaData() is called. + +Changes in 2.6.1 + + * issue 821 if a disconnection class exception is thrown during initial connection + setup, do not set the flag that indicates that checkDriverSupport() is complete. + + * issue 835 fix increased CPU consumption under heavy load caused by excessive + spinning in the ConcurrentBag.requite() method. + + * issue 817 updated behavior of new initializationFailTimeout, please see the + official documentation for details. + + * issue 742 add direct MXBean accessor methods to HikariDataSource for users who do + not want run run JMX. + Changes in 2.6.0 + * Redesign of the contention code path resulting in doubling contended throughput; now + contended pool access retains 98% of the uncontended throughput. + * 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 770 adding a new property initializationFailTimeout and deprecate configuration + * issue 770 add a new property initializationFailTimeout, and deprecate configuration property initializationFailFast. * issue 774 significantly improve spike load handling. @@ -40,6 +98,34 @@ Changes in 2.5.0 * HikariCP 2.5.0 and HikariCP-java7 2.4.8 have identical functionality. +Changes in 2.4.12 + + * issue 878 search for driverClass in both HikariCP class classloader and Thread Context + ClassLoader + +Changes in 2.4.11 + + * 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. + +Changes in 2.4.10 + + * 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. + Changes in 2.4.9 * issue 719 only reset lastConnectionFailure after a successful dataSource.getConnection() |