-----Original Message----- From: Josh Gooding [mailto:josh.good...@gmail.com] Sent: Friday, October 30, 2009 1:11 PM To: Tomcat Users List Subject: Re: ConnectionPool question
This is not bad, but there is NO PLACE in the code that actively closes all of the resources. Sometimes the code is LUCKY to have a call that is to rs.close(); but I am more than positive that there is no statement / connection closing going on. The hardest part is that everything is mixed into the presentation layer. I'll fix the DAO first, then move to more back-end fixing. Thanks for the 411 about the StatementFinalize and the Millis timeout. The millis has been changed to 54000 (15 seconds), and I'll look up more info about the StatementFinalize and the validationQuery. ======================================= You REALLY need to get this fixed though; you'll have crazy leaks all over the place. I battled this very thing for a while! This biggest problem I'm having is that I'm the only coder in a .NET shop (they all run IIS and code in .NET only) and no one has experience with TC except me. Honestly if it wasn't for this list and the sun forums, I'd be sunk on most things Tomcat / java wise. This list with the members have been an invaluable asset to my learning Tomcat. ============== Yeah, I feel your pain, too. Similar situation here. I have to hand-hold all of the server admins because they don't have the confidence or knowledge to do this stuff, and I don't have the permissions to touch the servers!! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
