I used my standalone setup and deployed your cluster-demo.war and the replication works. Could the problem be related to CDI SessionScope?
I saw this issue https://bugzilla.redhat.com/show_bug.cgi?id=900378 but I have not configured <replication-trigger>SET</replication-trigger>
So you have tried clusterbench/clusterbench · GitHub and it doesn't work?
What doesn't work?
How are you testing?
Maybe a test issue, are you sure you are sending the same cookies? Make sure you are accessing the load balancer URL, not AS directly via 8080.
I just cloned clusterbench and built clusterbench-ee6.ear. I deploy it unexploded in the deploy folder of both servers.
I open http://127.0.0.1:6666/clusterbench/cdi in apache, I can refresh the page to increment the number. I Ctrl-c the command window which runs the instance handling the sticky session. I make a new request and the counter is back to 0.
Interesting thing is if I start the instance again and close down the running one the seesion is restored to the previous number.
There are no exceptions in the log.
Radoslav Husar skrev:
Are you using exploded deployments?
There is a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1029099
The problem is that it associates the session with the full path of the deployment? Altough im not using exploded deployment both instances are in the same machine so the paths are different.