Thanks everyone for replying. We ended up trying some other configurations and found that moving to an ASYNC replication-type (configured in jboss-web.xml) eliminated the "downtime" we were seeing.
I'm just speculating and Bela can correct me if I'm wrong but in a SYNC replication-type with many replication-triggers being fired the up node must do some final negotiations (verifications) in order to be sure that the modified session attributes do not need to be delivered to the now down node. This final SYNC negotiation is what causes the up node to become unresponsive. However, in ASYNC the up node can que the modifications while it determines if it's partner node is really down while it continues to service other incoming requests. Obviously, one trades off the guarantee of session replication prior to response when one moves to an ASYNC type, but we have yet to see any issues. Again, these are just my observations. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848504#3848504 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848504 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
