On 27/06/2013 22:03, Mark Eggers wrote: > Getting a first start on where your leaks are is pretty easy as well. > > 1. Load your web application > 2. Run it to generate the leak > 3. Unload it from Tomcat using the manager app (or any other method) > 4. Do a Find Leaks from the manager app (or garbage collection from > VisualVM) > 5. Do a heap dump > 6. In the classes, look for org.apache.catalina.loader.WebappClassLoader > 7. Find the instance where the boolean started is false > 8. Right-mouse on the instance and search for nearest GC Root > 9. Find classes that you wrote and fix > > This gets the classLoader leak . . . others can be found by looking for > application - specific classes. > > Hope this helps.
This might be useful: http://people.apache.org/~markt/presentations/2010-11-04-Memory-Leaks-60mins.pdf Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
