HikariDataSource (HikariPool-1) has been closed.

[Darek Danielewski]

Quite often, every day actually, we get several of these error messages in our logs.

Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: HikariDataSource HikariDataSource (HikariPool-1) has been closed.

Could someone recommend what setting I should be looking at to improve stability? I sense it is a relation between JDBC timeout, DB session disconnect timeout, and HikariCP timeout settings. Any help is appreciated.

[ryan....@gmail.com]

What is managing your Hikari pool? You should only see this exception if the pool itself were closed, see here. Are you expecting the pool to be long lived i.e. the scope of your application (typical) or are you doing some more dynamic management of the pool that involves teardown at runtime? You should also be able to see the logging when the pool closes here to narrow down what is closing the pool.

[Darek Danielewski]

There is no special pool management, and the lib is running with mostly defaults inside a Spring Boot application. 

[Darek Danielewski]

And yes ... we do see "Shutdown initiated" in our logs. Although, can't say that's deliberate. Some event on Spring Boot side is causing this. Will have to investigate, unless you already have some tips.