光 HikariCP・A solid, high-performance, JDBC connection pool at last.
Apache License 2.0
19.84k
stars
2.92k
forks
source link
Failed to validate connection Pooled connection wrapping physical connection (Connection has been closed.). Possibly consider using a shorter maxLifetime value. #1755
Hi everybody,
I am working on a Spring MVC project (Spring version 4.1.1) and I configured HikariCP as connection pool manager.
When the application is not used for a while, it seems like Hikari starts loosing connections with DB, and when I try to connect to the web app, Tomcat shows this:
Here is my Hikari datasource configuration for Spring:
I already tried to use shorter maxLifetime values, as suggested by the stacktrace, but it did not make any difference.
Could anybody please help me resolving this issue? What am I doing wrong?
Hi everybody, I am working on a Spring MVC project (Spring version 4.1.1) and I configured HikariCP as connection pool manager. When the application is not used for a while, it seems like Hikari starts loosing connections with DB, and when I try to connect to the web app, Tomcat shows this:![image](https://user-images.githubusercontent.com/12703022/110924308-30747f80-8322-11eb-8c23-80570852e822.png)
Here is my Hikari datasource configuration for Spring:![image](https://user-images.githubusercontent.com/12703022/110922776-66186900-8320-11eb-9707-d2d850a9b465.png)
I already tried to use shorter maxLifetime values, as suggested by the stacktrace, but it did not make any difference.
Could anybody please help me resolving this issue? What am I doing wrong?
Other useful info: