-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Connection leak in application because it fails to close pooled connections #2174
Comments
Hi, were you able to find any solution? |
Hello @psneha716, can you share your Hikari/hibernate/jpa config? |
Hi @oucem00decat, #Hibernate config #Hikari config |
Hi team,
We've been facing the following issue since quite sometime in our application that the number of active connections goes upto 50(max) and the connections are not returned back to the pool. Have enabled ProxyLeak detection which reports leaks for all the active connections and they are released only when the application is restarted/an OOM error happens which forces the application to restart. Any help will be greatly appreciated. Thanks in advance!
Spring data jpa + Hibernate + jdbc
Jdk: 18
DB: Postgresql (42.3.5)
Hikaricp: 4.0.3
Spring boot: v2.7.0
Tried setting spring.jpa.properties.hibernate.connection.release_mode=after_transaction, bit it didn't work.
Logs:
One such connection leak log:
The text was updated successfully, but these errors were encountered: