"[EMAIL PROTECTED]" wrote : Hard to say. This message means that a timer has kicked in as a second line of defense, to prevent indefinite blocking. One reason could be that your system was severely overloaded, and you never got the RESUME_STABLE event. Another reason: your state was large (is that true ?), and state transfer took a long time. | I'd have to look at the logs to be able to say more about this.
Hello, I have similar problem: the second node is started extremely slow (30 min.) and the mentioned message is logged. The system was idle at the time, so I guess I have the large state situation. Correct me if I am wrong, but for me state means SFSBs and HTTP sessions. And I don't have a single SFSB or http client (the first node is started fully and sits idle, then the second node is started and meanwhile noone is using the application). Any ideas? Thanx in advance, nts View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907224#3907224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907224 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
