]
Jason Greene reassigned WFLY-157:
---------------------------------
Assignee: Paul Ferraro (was: Jason Greene)
fix invalid assign
Stale session data received when using DIST SYNC on node shutdown
-----------------------------------------------------------------
Key: WFLY-157
URL:
https://issues.jboss.org/browse/WFLY-157
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
Labels: as713tracking
Fix For: 8.0.0.Alpha1
There are few occurrences when client received older data even when using DIST SYNC.
http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x...
{noformat}
./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned:
hAzyrOe0KxA51coCNbSMUsrZ
./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf18
./perf17.log:2012/05/13 17:14:11:542 EDT [INFO ][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed.
perf18 -> perf21
./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data:
<org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data
received. Expected 37, received 36, Runner: 968>
./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] SFCORE_LOG - Error
sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale
session data received. Expected 37, received 36, Runner: 968>
./perf17.log:2012/05/13 17:21:20:224 EDT [INFO ][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed.
perf21 -> perf19
./perf17.log:2012/05/13 17:23:01:507 EDT [INFO ][Runner - 968] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed.
perf19 -> perf21
{noformat}
No logging about the session (hAzyrOe0KxA51coCNbSMUsrZ) in the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: