[
https://issues.apache.org/jira/browse/TRINIDAD-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Sullivan resolved TRINIDAD-1779.
--------------------------------------
Resolution: Fixed
Fixed in Trunk--revision 936599
Fixed in 1.2.x--revision 936601
Fixed in 1.2.12.3--revision 936602
Switched from storing the active page state object in the session to storing
the token for the active page state object. This still allows us to retrieve
the active page state object, but avoids having the servlet engine serialize
the page state object twice when configured for high availability
> Duplicate Attributes require too much memory
> --------------------------------------------
>
> Key: TRINIDAD-1779
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1779
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Environment: Generic
> Reporter: Scott Oaks
> Assignee: Blake Sullivan
> Attachments: JIRA-1779.patch, TRIN_1779_12x.patch,
> TRIN_1779_1_2_12_3.patch
>
>
> When saving a request, trinidad is creating an attribute named
> org.apache.myfaces.trinidadinternal.application.VIEW_CACHE.<id> which
> references a page state
> (org.apache.myfaces.trinidadinternal.application.StateManagerImpl$PageState)
> and also creates an attribute named
> org.apache.myfaces.trinidadinternal.application.StateManagerImp.ACTIVE_PAGE_STATE
> which references the same page state object.
> On single VM instances, this isn't an issue as the referenced object will be
> the same. But on distributed systems, depending on the replication mechanism
> used, this can lead to two copies of that page state object. [Consider the
> case of an appserver that saves the HTTP session to a database, which will
> lose all object reference information.]
> As the page state object is quite large (I typically see its serialized state
> require 150000 bytes), duplicating that memory requirement has an enormous
> impact on the performance of distributed systems. Additionally, it is then
> possible that after a replication that doesn't preserve the object
> references, the behavior of the application might be affected.
> From Max Starets:
> Perhaps the ACTIVE_PAGE_STATE could be referring to the state token (id)
> instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
