[jboss-jira] [JBoss JIRA] Closed: (JBAS-3591) For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry closed JBAS-3591.
----------------------------------

    Fix Version/s:     (was: JBossAS-5.0.0.CR2)
       Resolution: Won't Fix


The org.jboss.ha.framework.server.SimpleCachableMarshalledValue class we now use doesn't have the problem of increasing memory footprint. On the remote nodes it leaves the session as a byte[] until accessed following failover, which *should* help perf by deferring deserialization (needs to be tested). Leaving the data in SimpleCachableMarshalledValue also has the advantage of allowing web app undeploy to trigger conversion of cached objects to byte[] rather than removing them from the cache.  Doing this allows a shared cache to survive a single webapp redeploy w/o becoming inconsistent with the rest of the cluster and w/o leaking classloaders.

> For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on
> ---------------------------------------------------------------------------------
>
>                 Key: JBAS-3591
>                 URL: https://jira.jboss.org/jira/browse/JBAS-3591
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> Storing session or attributes in the cache as byte[] or MarshalledValue is unnecessary if region based marshalling is used.  Doing it greatly increases the memory footprint of distributed sessions.
> Need to benchmark the performance impact of this (could be positive or negative), although the memory savings would outweigh all but a major performance loss.
> Can't do this in Branch_4_0 is it breaks binary compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira