It's been a while since I looked at JBoss clustering code, but it sounds like a problem I encountered in the past:
The problem is with the HTTP session replication: When you login (or, do something that reads or writes to the HTTP Session context), JGroups tries to replicate it to all other nodes in the cluster. What JGroups does, is send a message to all the cluster members (and wait for an ACK). If, for some reason, it failes to get a receive enough ACKs (if there are 10 cluster members, it should receive 10 ACKs) then it waits until some timeout expires. This timeout used to be hard coded to 60 seconds, and I think it was changed to being configurable form the XML file. Also, this used to happen when for some reason, we had the same server multiple times in the node list of the cluster (and therefore the sender doesn't receieve enough ACKs). Try moving some of the JGroups logs to DEBUG and see if all the servers have the same view of the cluster. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891627#3891627 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3891627 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
