- !! 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
Mark Thomas interview on DZone
Related issues
- 48837 - Memory leaks protection does not cure leaks triggered by JSP pages code