[TAP5-2411] Tapestry webapp leaks a ThreadLocal

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-ioc
• Assignee: Jochen Kemnade
• Reporter: Jochen Kemnade
• Created: 31/Oct/14 12:07
• Updated: 06/Nov/14 10:43
• Resolved: 06/Nov/14 09:36

Description

When re-deploying a Tapestry webapp in a Tomcat container, I often see a warning like this:

21-Oct-2014 12:03:37.349 SEVERE [http-nio-9280-exec-14] org.apache.catalina.loader.WebappClassLoader.checkThreadLocalMapForLeaks The web application [/webapp] created a ThreadLocal with key of type [org.apache.tapestry5.ioc.internal.services.PerthreadManagerImpl.
MapHolder] (value [org.apache.tapestry5.ioc.internal.services.PerthreadManagerImpl$MapHolder@55d6dc57]) and a value of type [java.util.HashMap] (value [{1=DEFINED, 2=DEFINED, 3=DEFINED, 4=DEFINED, 5=DEFINED, 6=DEFINED, 7=DEFINED, 8=DEFINED, 9=DEFINED, 10=DEFINED, 
11=DEFINED, 12=DEFINED, 13=DEFINED}]) 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.

I'm not yet sure where this comes from. It looks like a Map<Number, org.apache.tapestry5.ioc.services.Status>.