If I'm getting my database connections from a JNDI resource (configured in server.xml) how do I destroy these suckers. Sample code would be great - or tell me to RTFM.
Matt -----Original Message----- From: Phillip Qin [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 8:04 AM To: 'Tomcat Users List' Subject: RE: Datasource connections not released when reloading context - to release your DB connections when your app is shutdown or reloaded: implement destroy method in your servlet class to close them. - to prevent connections getting exhausted, use evictor if your use commons pooling and dbcp. -----Original Message----- From: Jose Alfonso Martinez [mailto:[EMAIL PROTECTED] Sent: September 27, 2003 7:31 PM To: [EMAIL PROTECTED] Subject: Datasource connections not released when reloading context Hi guys, Does any one know if there is a possibility of tomcat, for any reason, to reload a context without telling it to do so???? I am having a problem that after 2 or 3 days without reloading tomcat, pooled-connections from the datasource get exahusted. The only case I have seen that the number of pooled-connections is incremented is when I reloaded my context. In this case, the reloaded context's datasource opened a new set of connections to work on (leaving the older connections opened and not releasing them until tomcat is shutdown). If the context gets reloaded over and over again, eventually connections with the DBMS will get exahusted... Is that the expected behavior???? To leave conections open when reloading a context???? Would there be another posibility for pooled-connections to get exahusted, once they were set up and correctly running??? Thanks in advance Jose --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
