Loading...

XML

Word

Printable

Workaround:

Workaround Exists
Workaround Description:

Hide

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>

<property name="inactiveOnStartup">true</property>

Show
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>  <property name="inactiveOnStartup">true</property>

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 !