[SANTUARIO-359] Possible memory leak when using Thread Pool

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Java 1.5.2
• Component/s: Java
• Security Level: Public (Public issues, viewable by everyone)
• Labels: memory-leak tomcat
• Environment: Windows Server 2008 x64, Tomcat 7.0.40, Java 1.6.0_43
• Assignee: Colm O hEigeartaigh
• Reporter: Vyacheslav Mayorov
• Created: 18/Jun/13 10:43
• Updated: 25/Jun/13 09:00
• Resolved: 25/Jun/13 09:00

Description

Tomcat warns about possible memory leak:

Jun 18, 2013 2:17:00 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/] created a ThreadLocal with key of type [org.apache.xml.security.utils.UnsyncByteArrayOutputStream$1] (value [org.apache.xml.security.utils.UnsyncByteArrayOutputStream$1@4d586d6a]) and a value of type [byte[]] (value [[B@687771d1]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Issue Links

• is a clone of: SANTUARIO-351 Avoid possible NPE in Unsync OutputStreams