This is a bit of a lead but it doesn't entirely solve it. It's only
cleaning up connections to one of the datasources, I still have
connections for 2 of them duplicated :(
If I get a chance I'll go digging some more based on the SO rabbit
hole, but I can mitigate the problem by restarting tomcat
I resolved the same using this link
https://stackoverflow.com/questions/11872316/tomcat-guice-jdbc-memory-leak
I created the ContextFinalizer to cleanup on shut down.
Also, I had loads of strange sql issues which were resolved by switching to
maria db.
Cheers Greg
On Thu, 13 Dec 2018 at
Hi, chris.
You can use apache commons-dbcp2-2.5.0.
This problem is fixed in this version.
And ServletContextListener is not necessary!
This is make you happy. :-)
Have a nice day!!!
2018년 12월 14일 (금) 오전 5:51, Chris Cheshire 님이 작성:
> Tomcat 9.0.12, Debian, MySQL Server 5.7.23, Connector/J
Tomcat 9.0.12, Debian, MySQL Server 5.7.23, Connector/J 5.1.46
I am trying to fix a lingering database connection problem. When I
reload a context via the tomcat manager, connections to the
datasources are not being released in mysql. They are still on the 30
second activity cycle from the
