[
https://jira.jboss.org/jira/browse/JBAS-7205?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-7205:
-----------------------------------
Component/s: Clustering
Web (Tomcat) service
Assignee: Brian Stansberry (was: Jean-Frederic Clere)
Moved from MODCLUSTER_101, as mod_cluster has no responsibility for session state.
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
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