[
https://issues.apache.org/jira/browse/MYFACES-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921323#action_12921323
]
Bruno Aranda commented on MYFACES-2942:
---------------------------------------
Using tomcat 7 I get this warning...
SEVERE: The web application [/editor-2.0-SNAPSHOT] created a ThreadLocal with
key of type [java.lang.ThreadLocal] (value [java.lang.threadlo...@41649a55])
and a value of type [org.apache.myfaces.config.RuntimeConfig] (value
[org.apache.myfaces.config.runtimecon...@33d063fd]) but failed to remove it
when the web application was stopped. This is very likely to create a memory
leak.
I don't know if the RuntimeConfig could be the one responsible of the leak in
Jboss?
> Memory Leak in MyFaces 2.0.1 probably as well in 2.0.2
> ------------------------------------------------------
>
> Key: MYFACES-2942
> URL: https://issues.apache.org/jira/browse/MYFACES-2942
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.1, 2.0.2
> Environment: JBOSS AS
> Reporter: Werner Punz
> Priority: Critical
>
> Stan Silvert from JBoss reports:
> I'm pretty sure 2.0.1 has a memory leak on undeploy. Mojarra had an undeploy
> leak and it took a long time to track it down. The same test I was using on
> Mojarra also failed on MyFaces but I haven't had time to track down the leak
> in MyFaces.
> Maybe this is fixed in 2.0.2? If not maybe someone can go ahead and take a
> look? The mem leak keeps MyFaces from passing TCK on JBoss AS. To test, all
> you need to do is create a small exploaded JSF app. Then have a script that
> touches web.xml every 10 seconds. That will cause the app to redeploy. You
> will get a PermGen error in about an hour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
