HikariCP · Issues· 544 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #2418
Hi
Updated Aug 19, 2026 - #2417
Connection number always equals to the maximum pool size, even if all connections are idle and minimum-idle is 1
Updated Aug 13, 2026 - #2413
Security: maskPasswordInJdbcUrl does not mask authority-embedded credentials (user:pass@host)
Updated Aug 6, 2026 - #2106
Fail Fast on bad credentials
Updated Jul 29, 2026 - #2404
Data sources without explicitly specified dataSource or dataSourceClass overwrite each others connectionTimeouts
Updated Jun 18, 2026 - #2374
HikariCP Connection Pool Cannot Recover After MySQL Connection Failure
Updated Jun 10, 2026 - #2397
Ensuring at least one connection is initialized before dependent framework bootstrap (Hibernate)
Updated Jun 6, 2026 - #2393
Is there a configuration in HikariCP to bypass automatic rollback of connection transaction state on close?
Updated Apr 2, 2026 - #2156
Hikari doesnt open more than 10 connections, even when maximumPoolSize and minimumIdle are greater than 10
Updated Feb 18, 2026 - #2389
Make HikariCP GraalVM native image ready
Updated Feb 17, 2026 - #2388
Yuck
Updated Feb 16, 2026 - #2380
Bag
Updated Jan 14, 2026 - #2379
[Feature Request] Use seconds as base unit for metrics in PrometheusHistogramMetricsTracker
Updated Jan 12, 2026 - #2378
Potential connection starvation due to DiscardPolicy usage in addConnectionExecutor
Updated Jan 8, 2026 - #1949
Issue HikariPool-6 - Connection is not available, request timed out after 300000ms. postgres 11.0 database and Hikari pool
Updated Jan 8, 2026