[
https://jira.jboss.org/jira/browse/MODCLUSTER-101?page=com.atlassian.jira...
]
Bela Ban commented on MODCLUSTER-101:
-------------------------------------
This is probably not even a mod-cluster issue, but a Clustering issue.
I can also simply touch the session.war (META-INF/web.xml) or simply the WAR is not
exploded): the session is redeployed but the session state is not re-acquired !
Redeployment of session doesn't acquire session state
-----------------------------------------------------
Key: MODCLUSTER-101
URL:
https://jira.jboss.org/jira/browse/MODCLUSTER-101
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Reporter: Bela Ban
Assignee: Jean-Frederic Clere
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