4 Replies Latest reply on Mar 24, 2014 10:05 AM by yguillerme69

Jboss 5.1 failover takes a lot of time

cubatura Oct 1, 2013 3:01 AM

Hello Everybody

I have 2 nodes jboss cluster running on 5.1 AS.

I'm trying to test the cluster behaviour in the case of network failure,

When I plug-off network cables from the first node (actually down ports on Cisco switch) I see that second node starts failover quickly:

2013-09-24 13:42:53,512 INFO [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] (Incoming-18,172.21.17.139:42254) JBoss Messaging is failing over for fa  
 iled node 1. If there are many messages to reload this may take some time...

But it takes about 25 minutes to complete it:

2013-09-24 14:07:47,279 INFO [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] (Incoming-18,172.21.17.139:42254) JBoss Messaging failover completed

Once failover is completed the system starts working properly,

I managed to find only one parameter about failover complete in deploy/messaging/messaging-service.xml, I set it as

<attribute name="FailoverCompleteTimeout">90000</attribute>

But it didn't help.

Could you please advise? thank you!

1. Re: Jboss 5.1 failover takes a lot of time

rhusar Oct 1, 2013 8:33 AM (in response to cubatura)

[Discussion moved from Clustering to JBoss Messaging]
Actions
2. Re: Jboss 5.1 failover takes a lot of time

yguillerme69 Mar 24, 2014 5:05 AM (in response to cubatura)

We encounter again this issue.
Can we fix that with a configuration change or is it a bug from this JBoss version?
Actions
3. Re: Jboss 5.1 failover takes a lot of time

rhusar Mar 24, 2014 9:08 AM (in response to yguillerme69)

How many messages are being reloaded on failover?
Actions
4. Re: Jboss 5.1 failover takes a lot of time

yguillerme69 Mar 24, 2014 10:05 AM (in response to rhusar)

We encounter the issue in low traffic (~1 messages) or standard traffic (~10 messages in the JMS Queue).
We encounter this issue only when we have network latency between nodes.
But we have a redundant link it should not appear ...

<jboss>/deploy/messaging/messaging-service.xml
-          <attribute name="DefaultMaxDeliveryAttempts">2</attribute>
-          <attribute name="FailoverStartTimeout">10000</attribute>
-          <attribute name="FailoverCompleteTimeout">30000</attribute>

<jboss>/deploy/messaging/remoting-bisocket-service.xml
-          <attribute name="timeout" isParam="true">10000</attribute>

After we have tried to increase the FailoverCompleteTimeout without success.
Actions

Go to original post