click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Finn Bock (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CLK-706) undeploy in tomcat prints warnings of thread local ContextStack
Date Tue, 29 Jun 2010 14:36:50 GMT

     [ https://issues.apache.org/jira/browse/CLK-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Finn Bock resolved CLK-706.
---------------------------

    Fix Version/s: 2.3.0-M1
       Resolution: Fixed

fixed in trunk

> undeploy in tomcat prints warnings of thread local ContextStack
> ---------------------------------------------------------------
>
>                 Key: CLK-706
>                 URL: https://issues.apache.org/jira/browse/CLK-706
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.2.0
>         Environment: Tomcat 6.0.26
>            Reporter: Finn Bock
>            Assignee: Finn Bock
>            Priority: Minor
>             Fix For: 2.3.0-M1
>
>
> With tomcat 6.0.26 on windows, starting the examples app, browse a page and press crtl-C
in the tomcat window causes tomcat to complain about a possible memory leak:
> SEVERE: A web application created a ThreadLocal with key of type [java.lang.ThreadLocal]
(value [java.lang.ThreadLocal@bf015]) and a value of type [org.apache.click.Context.ContextStack]
(value [[]]) but failed to remove it when the web application was stopped. To prevent a memory
leak, the ThreadLocal has been forcibly removed.
> It is caused by Context.hasThreadLocalContext() which creates an empty ContextStack if
none existed before. Which is called by PerformanceFilter's attempt to find the application
version number.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message