myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabrielle Crawford (Updated) (JIRA)" <>
Subject [jira] [Updated] (TRINIDAD-2152) token cache pinning session attribute map
Date Fri, 21 Oct 2011 23:48:32 GMT


Gabrielle Crawford updated TRINIDAD-2152:

    Resolution: Fixed
      Assignee: Gabrielle Crawford
        Status: Resolved  (was: Patch Available)
>  token cache pinning session attribute map
> ------------------------------------------
>                 Key: TRINIDAD-2152
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 2.0.2-core
>            Reporter: Gary VanMatre
>            Assignee: Gabrielle Crawford
>         Attachments: TokenCache-trunk.patch, TokenCache-trunk.patch
> Stevan Malesevic found that the token cache is pinning the session map. 
> com.sun.faces.context.ExternalContextImpl will create a instance of com.sun.faces.context.SessionMap
on every request. SessionMap points to 
> Request object. However this is per request so it is not carried over between requests.
 Now, the reason why we always have request object pined between requests is Trinidad code
TokenCache which pins the owner (SessionMap) which would otherwise be gc-ed.  From what I
can see 
> Trinidad code can be changed to always get extContext.getSessionMap() instead pinning
it permanently. This will make sure we are not pinning Request object and all its attributes
in between requests. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message