> From: kwal...@sbceo.org [mailto:kwal...@sbceo.org] > Subject: RE: Connection Pool Exhausted > > where do I look to see what connection doesn't get closed > like it should?
Now you've reached the hard part. You'll need to take thread dumps to find out what threads are running and where they are. Most will be stuck in the connection pool, waiting for one to come available - that will tell you where the connections are being acquired, and you should follow the logic from there to make sure the code is using a finally clause to guarantee connections are being closed. You should also look at threads not waiting in the pool, since one of those may well have acquired your one and only connection and is now stuck somewhere else. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
