HikariCP

HikariCP copied to clipboard

The pool didn't recover after AWS RDS failover

4

We have an application that runs on AWS/EKS and is using Amazon's RDS for Postgres. The application has been running fine for quite some time till this Monday when after...

vraikov

BigInteger cannot be cast to java.lang.Long

3


guohaowei0813

Hikari cp unable to make new connections after connection has passed maxlifetime

9

#### Environment ``` HikariCP version: 2.7.9 JDK version : 1.8.0_111 Database : Oracle Driver version : 0jdbc6 11.1.0.7.0 Hi, is this issue resolved? I am facing similar issue where Hikari...

rawatkav

Connection Timeout with Oracle/Mongo and Spring Data JPA

5

Hello everyone, We are facing a lot of Connection Timeout issues with Hikari Connection Pool that comes with Spring Boot 2.x. We have two databases (Mongo and Oracle) and I...

hardikdesai81

maxLifeTime(20000) millisecond value less than wait_timeout(28800) second

10

@csc365kl agree with that, and i have a same question?Is that a bug or not?how shold i do? _Originally posted by @jerry100chan in https://github.com/brettwooldridge/HikariCP/issues/1483#issuecomment-642406054_

jerry100chan

See commit message.

gontard

Has/will the connection pool race condition fix that was added in 5.0 be back ported to the older versions? Specifically the jdk 8 maintenance 4.0 builds? We're currently running into...

jonatino

Anouar199

FATAL: terminating connection due to idle-in-transaction timeout

1

When PostgreSQL uses Hikari connection pool, it often reports an error by using cursor:“FATAL: terminating connection due to idle-in-transaction timeout” The configuration is: Error screenshots are:

linht12

Currently a check is scheduled when a connection is opened, it waits for the timeout on a ScheduledExecutorService. It's usually cancelled. That is not very useful when you have real...

coladict