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

Leonardo Uribe commented on MYFACES-3549:
-----------------------------------------

But the code doesn't solve the behavior described in MYFACES-3510. First of 
all, the current code, the previous code, and the code proposed here has no 
memory leaks. What we want here is a way to prevent collect that map when the 
server is running out of memory, but release it as soon as the app is 
undeployed. Remember in these days it is possible to find different web 
applications sharing the same myfaces jars, so we also don't want situations 
where some classloader is not released because other application has a strong 
reference to the map and through that way to the discarded classloader.
                
> Alternative solution to bugs MYFACES-3262 and MYFACES-3510
> ----------------------------------------------------------
>
>                 Key: MYFACES-3549
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3549
>             Project: MyFaces Core
>          Issue Type: Improvement
>    Affects Versions: 2.1.7
>            Reporter: Jesús Pérez Alcaide (ISBAN)
>         Attachments: AAA_patch_PropertyDescriptor_MyFaces217.jar, 
> MyFaces3262_PropertyDescriptorHolder.patch, 
> MyFaces3510_AbstractFacesInitializer.patch, 
> MyFaces3510_ComponentAttributesMap.patch
>
>
> I would like to propose an alternative solution to bugs MYFACES-3262 and 
> MYFACES-3510, which consists in rollback the changes made in MYFACES-3510 and 
> modify the solution given in MYFACES-3262 by adding a soft reference to the 
> methods held in the class _PropertyDescriptorHolder.
> This alternative solution fixes MYFACES-3262 and avoids the performance loss 
> caused by MYFACES-3510.
> More information in this email:
> http://markmail.org/message/xh66wlte6luqn63d

--
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