[TRINIDAD-2152] token cache pinning session attribute map

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1-core
• Fix Version/s: 2.0.1-core
• Component/s: Components
• Assignee: Gabrielle Crawford
• Reporter: Gary VanMatre
• Created: 21/Oct/11 13:11
• Updated: 21/Feb/12 20:41
• Resolved: 21/Oct/11 23:46

Description

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.