Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification.
The "MemoryLeakProtection" page has been changed by SylvainLaurent. http://wiki.apache.org/tomcat/MemoryLeakProtection -------------------------------------------------- New page: ''' !! This page is under construction !! ''' For some time Tomcat has had some means of protection against memory leaks when stopping or redeploying applications. This page tries to list them, and shows the situations where leaks can be detected and fixed. = Diagnose a classloader leak upon request = = Different types of leaks that Tomcat can detect (or not) = == ThreadLocal leaks == === Custom ThreadLocal class === === Webapp class instance as ThreadLocal value === === Webapp class instance indirectly held through a ThreadLocal value === == ThreadLocal pseudo-leak == == Threads ContextClassLoader == === Threads spawned by JRE classes === === Threads spawned by classes loaded by the common classloader === === Threads spawned by webapps === == Child classloaders == == static class variables == == LogFactory == == JavaBean Introspector cache == == JDBC driver registration == == RMI target == = Summary matrix = ---- == References == [[http://java.dzone.com/articles/memory-leak-protection-tomcat|Mark Thomas interview on DZone]] Related issues * [[https://issues.apache.org/bugzilla/show_bug.cgi?id=48837|48837]] - Memory leaks protection does not cure leaks triggered by JSP pages code * --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
