Thanks, much clearer :)
What you're doing sounds fine, and the behavior you report sounds like a bug. So I
searched JIRA for 4.0.1 bugs and found
http://jira.jboss.com/jira/browse/JBAS-60. That
would cause the symptom you report -- once the session is active on cluster A the manager
is unaware of replication traffic from the other node. It was fixed for 4.0.2.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964235#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...