[jboss-jira] [JBoss JIRA] Updated: (JBAS-7205) Redeployment of session doesn't acquire session state

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-7205:
-----------------------------------

    Workaround Description: 
Edit the server/<config_name>/deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml file. Find the "standard-session-cache" configuration section and set the following properties to "true"

         <property name="useRegionBasedMarshalling">true</property>
         <!-- Must match the value of "useRegionBasedMarshalling" -->
         <property name="inactiveOnStartup">true</property>
                Workaround: [Workaround Exists]


Added a workaround. 

I'm debating whether to make useRegionBasedMarshalling=true the default for AS 5.2. The reason to do it is it's the correct fix for this issue.  The downside is it adds some overhead to replication. I suspect deploying multiple distributable webapps in the same AS and then independently hot redeploying is a bit of an edge case; more common are just a single webapp, or multiple webapps packaged in an ear, or full server restarts when applications are upgraded.

> Redeployment of session doesn't acquire session state
> -----------------------------------------------------
>
>                 Key: JBAS-7205
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7205
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Bela Ban
>            Assignee: Brian Stansberry
>         Attachments: web.war
>
>
> Here's the scenario:
> - Start instances A and B in a cluster, the webapp is session.war (*exploded* WAR)
> - Create a session, say its session-id is sessionId.A
> - Go to A and remove the WAR, e.g. cd ./deploy ; mv session.war session.war.bak
> - Refresh the session. It fails over to B: sessionId.B
> - Go back to A  (/deploy dir) and mv session.war.bak session.war
> - Go to B and remove the session
> ==> The session will fail back to A, but the session's data is gone !

-- 
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