[ 
https://issues.apache.org/jira/browse/MYFACES-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922527#action_12922527
 ] 

Martin Kočí commented on MYFACES-2942:
--------------------------------------

With EL 2.2 implementation from Glassfish, tomcat 6.0.X and myfaces 
helloworld20 archetype,  instance of 
https://uel.dev.java.net/svn/uel/trunk/api/src/main/java/javax/el/BeanELResolver.java
 holds reference to HelloWorldController.class in:

private static final ConcurrentHashMap<Class, BeanProperties> properties =   
new ConcurrentHashMap<Class, BeanProperties>(CACHE_SIZE);

and keeps the classloader alive. This is cleary problem in this particular EL 
implementation. After I commented out that caching, classloader is GCed. 

Tomcat uses better solution:
 
http://svn.apache.org/viewvc/tomcat/trunk/java/javax/el/BeanELResolver.java?revision=1022623&view=markup

so this problem should not be general.









> 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
>            Assignee: Jakob Korherr
>            Priority: Critical
>         Attachments: MYFACES-2942-RuntimeConfig.patch
>
>
> 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.

Reply via email to