jxin19
commented
4 years ago did u changed set maxLifetime?
Open satscreate opened 5 years ago
jxin19
commented
4 years ago did u changed set maxLifetime?
satscreate
commented
4 years ago did u changed set maxLifetime?
I kept it as default every properties, as below,
HikariPool-1 - configuration:
allowPoolSuspension.............false
autoCommit......................true
catalog.........................none
connectionInitSql...............none
connectionTestQuery.............none
connectionTimeout...............30000
dataSource......................none
dataSourceClassName.............none
dataSourceJNDI..................none
dataSourceProperties............{password=
brettwooldridge
commented
3 years ago Can you get a thread dump while the pool population is in the process of declining?
Problem:
Using spring boot application with hikari configured as below
Hikari Config:
And everything works well with below successful pool status,
And every time i access the pool connection it add connection to active and clear back to the same status within seconds.
After 2 to 3 days suddenly application instance getting crashed without any logs in Spring. As i enabled the TRACE mode log in application the last log which shows related to hikari and connection pool as below,
Right exactly from the starting of the spring log, the connection getting dropped from total pool size as below.
HikariPool-1 - Pool stats (total=99, active=0, idle=99, waiting=0)
--omitted
HikariPool-1 - Pool stats (total=0, active=0, idle=0, waiting=0)
No trace of kill signal by the way. below is the spring log
Spring.log
What must be wrong in this process? And why this sql connection logs above shows like closing a socket? and why did hikari suddenly dropping the connections and tomcat process also dies. Please help.