-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hikaricp maintaining the closed connections, the other threads in the application getting the Connection is closed issue #2282
Comments
I can see the same from my side with tons of:
I'm using Spring Boot 3.4.2 where the Hikari dependency as well as the PostgreSQL JDBC driver one come from the Spring Boot BoM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In one of our application, we are suspecting the behavior of hikaricp maintaining the closed connections.
One connection is closed by the database server , the expectation is this connection must not maintained in the pool and must not be re used by the other threads, but we observed that the same connection is being used by the other threads.
We are using the MYSQL 8 database and Mariadb driver (mariadb-java-client-2.2.6) and HikariCP-5.0.1, we did not set the test query as jdbc4.0 is being used the test connection would be use isValid() method on connection object.
The application is developed using the Spring 5.3.32, hibernate 5.3.30.
I am going through the latest releases and commits from HIKARI CP , I found the following merge request , will it close the bug which i am reporting above?
merged #2157 close connections marked as evicted instead of returning them to the pool
The text was updated successfully, but these errors were encountered: