Issue Type: Bug Bug
Affects Versions: 1.4.3.GA
Assignee: Unassigned
Components: JMS Clustering
Created: 19/Jun/12 12:29 AM
Environment: 4.3.0.GA_CP07 (build: SVNTag=JBPAPP_4_3_0_GA_CP07 date=200911251949)


we have 4 nodes clustering, while one of them have long GC pause, which cause this node(node52) drop of clustering, and having the following log

2012-06-14 03:27:48,277 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@6225352b got new view [10.164.218.18:7910|10] [10.164.218.18:7910, 10.164.107.69:7910, 10.164.107.65:7910], old view is [10.164.218.14:7910|9] [10.164.218.14:7910, 10.164.218.18:7910, 10.164.107.69:7910, 10.164.107.65:7910]
2012-06-14 03:27:48,277 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] I am (10.164.218.18:7910)
2012-06-14 03:27:48,998 INFO [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] JBoss Messaging is failing over for failed node 52. If there are many messages to reload this may take some time...

can anyone tell me where can I config the timeout of the clustering node drop? It seem 2 minutes in my case, but I can't find in each configuration files...
Project: JBoss Messaging
Priority: Blocker Blocker
Reporter: Bond Chan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira