On 3/24/2018 5:36 AM, Filippo Machi wrote:
Hello Shawn, about this question, are you sure that none of the webapps running on those tomcats are connecting to the database without using the pools configured in the context.xml? Creating other pools or performing direct connections? That could explain while changing the configuration you are not able to limit the number of connections neither to mitigate the problem with removedAbandoned configuration.
That code isn't familiar to me. I do have access to it, but there is a LOT of it. I've looked over a little bit of it.
I cannot be ABSOLUTELY sure that this isn't happening, but I very much doubt that it is. All of the developers know that there are connection pools provided in the servlet context, so I don't think they would try to handle it themselves. I will ask, and hope they don't bite my head off TOO severely. :)
I have already risked death by telling the developers that they're closing JDBC resources incorrectly, which I suspect is the root cause of our troubles. I will be pursuing a solution to this with them.
I will be attempting to lower the MySQL server-side wait_timeout from eight hours to one hour. Which is one of those things that shouldn't be necessary, but might clean things up when the developer's don't. I don't know if closing the connection on the server side will clean up all the objects in the application, or if there might be a resource leak. If there is a leak, then we are already facing it, because connections ARE closed at eight hours idle by the server. But I'd rather have that problem than the problem we currently have.
If there is anyone else with ideas, please reply to the original message! Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
