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

Leonardo Uribe commented on MYFACES-3510:
-----------------------------------------

No, it is not a bug. There is no other way to detect tomcat different to check 
if such class exists on the classpath. Instead, what do you need is implement a 
LifecycleProvider2 for glassfish or a custom LifecycleProviderFactory, to skip 
TomcatAnnotationLifecycleProvider.isAvailable. Unfortunately, since glassfish 
is CDDL/GPL licensed, we can't include that integration code in MyFaces. See:

https://cwiki.apache.org/confluence/display/MYFACES/Integration+with+application+and+web+servers

for more details. It could be good to share your findings later in a blog, 
other users have reported problems setting up myfaces with glassfish, and maybe 
that could help
                
> Application components classloader memory leak
> ----------------------------------------------
>
>                 Key: MYFACES-3510
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3510
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.1.6
>         Environment: WIndows Glassfish Embedded
>            Reporter: Ruben Martin Pozo
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.13, 2.1.7
>
>         Attachments: MYFACES-3510-1.patch, MYFACES-3510-2.patch, 
> screenshot-1.jpg
>
>
> We've seen an application classloader memory leak due to the new class 
> javax.faces.component._PropertyDescriptorHolder class introduced in version 
> 2.1.6
> This class holds a reference to a Method of a component loaded by the 
> application classloader. The memory leak shows up when the 
> _PropertyDescriptorHolder is stored in the _ComponentAttributesMap class that 
> is loaded by the system class loader.
> You should use a WeakReference instead of storing the direct reference to the 
> Method

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to