[jira] [Reopened] (TRINIDAD-1812) Memory use is very high in J2EE cluster with session replication (Weblogic) when using pageflowscope

["Mike Kienenberger (JIRA)" <de...@myfaces.apache.org>]

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

Mike Kienenberger reopened TRINIDAD-1812:
-----------------------------------------

 We don't have any active Trinidad committers currently. If you provide a patch in unified diff format from the root of the project, I will apply it. I've applied a number of IE11 fixes supplied by the community recently.

If you would like assistance in tracking down the problem and creating a solution, I recommend posting a message on the dev@myfaces mailing list to see if any other JSF developers have an idea.

> Memory use is very high in J2EE cluster with session replication (Weblogic) when using pageflowscope
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1812
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1812
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.7-core
>         Environment: Weblogic 10 and all versions forward.
>            Reporter: Nicolai Marck Ødum
>            Priority: Critical
>         Attachments: trinidad_demo_1.2.13.war, trinidad_demo_1.2.13_sources.jar
>
>
> In a Weblogic cluster with session replication the memory use (the size of the web session) is much higher on the server that has a copy of the session then on the primary server.
> The problem is related to multiple session attributes that have references to the same shared object in Trinidad. This design has a negative side effect with Weblogic because of the transitive closure ff session attributes. The shared object (and the object graph below it) is copied for each attribute.
> I have created a simple guide with a modified example of the demo application from Trinidad that shows the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)