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

["Nicolai Marck Ødum (JIRA)" <de...@myfaces.apache.org>]

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

Nicolai Marck Ødum reopened TRINIDAD-1812:
------------------------------------------


I have tried to build branches/trinidad/-1.2.x which has fix commited for trinidad-1779 (this issue is marked duplicate of 1779) and tested it with both our application and the special version of trinidad-demo attached. (Did a simple replace of the 2 trinidad jar files inside the war file) and I am still able to produce the problem.

I am also not able to apply any of the patches to my 1.2.13 source tree and one thing that I noticed is that patch says "public class StateManagerImpl extends StateManager" and when I look into the source tree I find that class says "public class StateManagerImpl extends StateManagerWrapper" - maybe the patch is for another source tree?


> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.