Dave I'm not sure what your in memory db is but here is how I handled a similar problem. My application uses connection pooling. I had problems with my connection pools not being cleaned up. I added a contextListener that keeps track of the pools and then when the context is destroyed it cleans up the pools. You could probably use the same technique for your in memory database.
Does this sound like what you are wanting to do? Michael -----Original Message----- From: David Vollberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 30, 2004 10:53 AM To: [EMAIL PROTECTED] Subject: cleaning up a removed webapp I am trying to upgrade one of the webapps running on my Tomcat instance(version 4.1.x). To do so, I am removing a webapp from my Tomcat instance by using http://localhost:8080/manager/remove?path=/app. This app is running an in-memory database that isn't being cleaned up. When I go to install a newer version of my app(using manager/install), I am getting out of memory errors. I want to avoid having to shutdown Tomcat because that would take other webapps offline. I know I could increase the memory size for the instance, but am looking for a cleaner solution. Is there a listener hook or method I can put code into to shut down the database and otherwise clean up the app before it is removed by Tomcat? Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
