That sounds like you are closing the stable door after the horse has bolted. Why not wrap a _try_ and _finally_ block around the code areas that create/open connections to prevent this?
Connections are a strange fruit and should always be closed; otherwise your app could run out of memory not just connections. Christopher Marsh-Bourdon www.marsh-bourdon.com -----Original Message----- From: Shailender Jain [mailto:[EMAIL PROTECTED] Sent: 09 May 2005 11:27 To: user@struts.apache.org Subject: Connection Leakage Hello All, I have got a application which is running live. (Struts with the usage of DBCP for connection pooling) We have found a problem that at many places we have not closed the connections. To solve this problem we thought of increasing the number of Maximum active connection. We are also thinking if there is a way by which we can configure the connection pool so that it should close the connection after some time if it is not done by the code. Thanks Shailender Jain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------------------------------------------- The information contained herein is confidential and is intended solely for the addressee. Access by any other party is unauthorised without the express written permission of the sender. If you are not the intended recipient, please contact the sender either via the company switchboard on +44 (0)20 7623 8000, or via e-mail return. If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. 3166 -------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
