This was fixed in 3.2.6 It was a bug in the jboss clustering hasingleton that meant it had to wait for a clustered method invocation to timeout before it detected the original server had failed.
Please, please, please - test the latest and greatest before posting in future. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852281#3852281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852281 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
