[picocontainer-scm] [jira] Created: (PICO-373) Logging about memory leaks and ThreadLocals when redeploying a picocontainer-using app on Tomcat 6.0

"David North (JIRA)" <jira-yCVjj/[email protected]> Wed, 14 Jul 2010 05:11:32 -0500 (CDT)
Newsgroups gmane.comp.java.picocontainer.cvs
Message-ID <26045249.12134.1279102292444.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Logging about memory leaks and ThreadLocals when redeploying a picocontainer-using app on Tomcat 6.0
----------------------------------------------------------------------------------------------------

                 Key: PICO-373
                 URL: http://jira.codehaus.org/browse/PICO-373
             Project: PicoContainer
          Issue Type: Bug
          Components: PicoContainer (Java)
    Affects Versions: 1.3
         Environment: Linux (Fedora Core 12)
            Reporter: David North
            Priority: Minor
         Attachments: threadLocalBugDemo.zip

Deploy the attached sample application onto Apache Tomcat v6 (included are a pre-built WAR exported from eclipse, a context file for tomcat, and the eclipse project containing the source code).

Now re-deploy by touching the war file.

Observe the following line in the catalina.out log file:

14-Jul-2010 10:52:02 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: A web application created a ThreadLocal with key of type [org.picocontainer.defaults.ConstructorInjectionComponentAdapter$1] (value [org.picocontainer.defaults.ConstructorInjectionComponentAdapter$1@f91da9]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

Is there some destroy/dispose/shutdown call on picocontainer that I am omitting, or is this a bug?

The following thread discusses the problem with Tomcat and ThreadLocals and makes a few suggestions for how to avoid it:
http://echo.nextapp.com/site/node/6254

I've marked this bug as minor since leaking Booleans isn't a serious memory leak, so it's really just the log spam that's upsetting.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

<hr/>
<p>
To unsubscribe from this list please visit:
</p>
<p>
    <a href="http://xircles.codehaus.org/manage_email">http://xircles.codehaus.org/manage_email</a>