You do not say which version of Tomcat you are using. But in general you can set the removeAbandoned* parameters to mitigate the problem (i.e. it will take longer to stop responding).
If using 5.5.x look for the heading "Preventing dB connection pool leaks" at: http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html HTH - Richard -----Original Message----- From: Charles P. Killmer [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 25, 2005 1:05 PM To: Tomcat Users List Subject: Tracking I have a bunch of JSP files that all instantiate a single class file. Is there a way for the class file to log which file called it and ideally from which line the call was made? My bigger problem is that I am using Connection pooling. And if I don't close every connection when I am down with it, the server stops responding. Restart Tomcat and everything is back to normal. Is there a setting to have Tomcat close all connections for me when a request finishes? Thank you for any thoughts. Charles --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
