Either session is not replicated correctly or replicated session is not detected on server-side. This causes the page to timeout on next request after a cluster node fails
Environment:
Setup JBoss cluster with 2 nodes. Create test app with ZK Maven Archetype for ee-eval.
Steps to reproduce:
1. Load index.zul (observe session id which shall contain node id for eg. YsMHmxDa9SEkur-N2nvGHB4P.standalone-nodeA)
2. Increase count by clicking count button
3. Stop/Terminate the current node serving requests from step 1 and 2
4. Click count once more
Expected:
Count is increased and session id should be same but with suffix changed to second node id YsMHmxDa9SEkur-N2nvGHB4P.standalone-nodeB)
Actual:
Page shows zk timeout message and have to reload. Completely new session is created to serve this new page load