Roc Chiu comments

Results 18 comments of


                                            Roc Chiu

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

HikariCP version is 3.4.5

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

@ismaan1998 Not yet！It takes a long time for this problem to recur.

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

@wanglunhui2012 No, I am not. It's spring boot auto config default value 30 minutes. After about 3 days of normal running, this problem occurred.

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

normal log: ``` 2020-12-28 00:02:30.472 DEBUG 28421 --- [Hikari connection closer] com.zaxxer.hikari.pool.PoolBase : Hikari - Closing connection oracle.jdbc.driver.T4CConnection@2f9129bc: (connection has passed maxLifetime) 2020-12-28 00:02:31.080 DEBUG 28421 --- [Hikari connection adder]...

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

``` spring: datasource: type: com.zaxxer.hikari.HikariDataSource url: **** username: **** password: **** hikari: poolName: Hikari auto-commit: false ``` With Spring Boot 2.2.x, it use `com.zaxxer.hikari.HikariConfig` default config value. > > @wanglunhui2012...

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

> Do you find any solution? @BilgehanYildiz Not yet, I have not found this problem in other environments, I guess it‘s problem from Oracle session or network.

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

> > When I use Spring boot auto configuaration with default HikariCP config, I get this erro, What happend ? > > ``` > > 2020-12-28 08:17:35.692 DEBUG 28421 ---...

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

My HikariCP version is 3.4.5, And I will upgrade it.

kernel: PBFT-1[50933]: segfault at 63 ip 00002b287fd2256d sp 00002b2883e573b0 error 4 in libnss_files-2.17.so[2b287fd1f000+c000]

![ebf5eb7e251e1c122b9a03fc2f86b4e6](https://user-images.githubusercontent.com/8520547/185823008-53223c4d-3793-4601-ada5-ca9f1e1715b9.jpg)

Connection is not available, request timed out after 3000ms and Pool stats (total=0, active=0, idle=0, waiting=0)

> Hi @PC-Chiu, did the newest version of Hikari fix the issue for you? Sorry!!! It only happens in certain circumstances, doesn't happen in any other environment and the original...