[jira] [Resolved] (TRINIDAD-2052) Native memory issue Defltaer/inflater from StateManagerImpl

["Stevan Malesevic (JIRA)" <de...@myfaces.apache.org>]

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

Stevan Malesevic resolved TRINIDAD-2052.
----------------------------------------

    Resolution: Fixed
    
> Native memory issue Defltaer/inflater from StateManagerImpl
> -----------------------------------------------------------
>
>                 Key: TRINIDAD-2052
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2052
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.13-core 
>            Reporter: Stevan Malesevic
>
> StateManagerImpl uses a session base deflater/inflater. Thye intention here was to reduce number of deflater/infalter objects laying around and finalizers from them. The issue is that these objects are holding onto native memory from zstream and this one gets released only when end() is called or finalizer is invoked
> What this means is that if one creates sessions fast enough number of deflaters staying around waiting for session to expire goes up , increasing native memory usage and causing jvm to run out of native memory easily on 32-bit system
> To prevent this we need to go back on creating deflater/inflater per invocation and calling end() when done. This should nto be that bad from perspective of finalizers as the object will mostlly be cleaned in end() method so finalizer should not hold onto any significant memory

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