Project: Tomcat
Bug 51688 JreMemoryLeakPreventionListener should protect against AWT thread creation
Reported: 2011-08-19 14:49:17 | Status: resolved fixed

Any webapp that calls java.awt.Toolkit.getDefaultToolkit will launch a new thread (AWT-Windows, AWT-XAWT, etc.) which will capture the ContextClassLoader, pinning the webapp in memory after an undeploy/redeploy. A simple addition to JreMemoryLeakPreventionListener can alleviate this condition.

Files changed in fix:
java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java