On Fri, 04 Feb 2005 17:45:12 -0600, Jonathan Wilson <[EMAIL PROTECTED]> wrote: > Someone else will be able to attest to this better than I, but there is > a known issue with the classloader [I think] that doesn't release memory > on a undeploy..eventually you'll run out of memory after a certain > number of deploy/undeploys. You could try using the jvm's -Xmx modifier > in your startup/catalina shell, which may buy you more time[guru input > here, please]...
Do you mean this ? http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 It turned out to be a JDK feature ;) > But my app starts up lightweight so I can schedule downtime a couple of > hours or so in advance, then drop tomcat for a few minutes while I > deploy manually. Maybe you could use the Manager: Stop the Service, > undeploy, stop TC, start TC, deploy the service using the Manager, start > service if necessary. It is indeed difficult to guarantee that everything will be cleaned up, unless the application is reasonably well written. In case of issues like usage of the bean instrospector as mentioned above, some explicit cleanup is required (now done automatically by Tomcat, but this will only be in the next release). See the bug report for info on workarounds. -- xxxxxxxxxxxxxxxxxxxxxxxxx R�my Maucherat Developer & Consultant JBoss Group (Europe) S�RL xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
