In jboss7 clustered environment how to bounce HornetQ mbeans on failover. Is it required?

[veenaonnet]

Hi,

In Jboss4, in a clustered environment we used to bounce(start/stop) queue mbeans on failover. It was done using "mejbStart", "mejbStop" methods.

"ServiceModule=destinations-service.xml,j2eeType=MBean,"

"name=jboss.messaging.destination-servicQueuename%3dMetaDataJobs",

However in jboss7 as HornetQ is used this is not relevant. There is mbean for every queue.

Is it required to call pause and resume method on those mbeans? Or can safely get rid of the old code and HornetQ will take care of failover as clustering is already enabled in standalone-full-ha.xml?

Regards,

Veena

[gaohoward]

You don't need to worry about the message failover with HornetQ clusters, it's dealt with transparently.

[veenaonnet]

Thanks for your response.

In jboss messaging, with clustering, when node went down all the in queue processes of the node were replicated to the up node and it process the messages,

However, with HornetQ if clustering is setup and node goes down then the messages in queue of a node are not processed by the up node. They get processed only once the node comes up.

Can this issue be solved without setting up HA(live/backup node)?

If HA is must for such scenarion, can collocated topology be used with jboss7.1.1 final and HornetQ2.2.13?

[jbertram]

Can this issue be solved without setting up HA(live/backup node)?

No.  You can't get fail-over without the proper configuration.

If HA is must for such scenarion, can collocated topology be used with jboss7.1.1 final and HornetQ2.2.13?

Yes, although I'd recommend you use a later version.

[veenaonnet]

Thanks Justin. Are you suggesting later version of jboss i.e EAP? Is it possible to use HornetQ2.3.0 with jboss7.1.1 final?

Will I run into the issues and what issues if used the current version(jboss 7.1.1 and HornetQ2.2.13)?

Currently, it is little difficult to upgrade to the new version of jboss.

Regards,

Veena

[jbertram]

I'm suggesting either EAP or building it yourself.  Lots of bugs have been resolved in both AS7 and HornetQ since 7.1.1 was released.

It is not possible to use HornetQ 2.3.0.Final with AS 7.1.1 - at least not without a bunch of modifications to the messaging subsystem.

[veenaonnet]

Thanks Justin,

[veenaonnet]

Hi Justin,

As per your suggestion I have build Jboss7.2.0 and used it to configured collocated HA with replication.

Failover and Failback works fine with data replication for the first time. However below scenario does not work.

  1. Kill first
server -> failover occurs

2. Start first
server -> failback occurs

3. Now HQ backup
on 2nd server must be restarted otherwise failover can't happen again

There is a bug logged:

https://bugzilla.redhat.com/show_bug.cgi?id=1013536

They have given 2 solutions:

1. It says, a parameter is added to hornetq (max-saved-replicated-journal-size)  to solve this issue but could not find the parameter in jboss cli/messaging xsd.

2. They have suggested a workaround
To restart the 2^nd server manually on failback. However we had to restart both the servers otherwise could not get RemoteConnectionFactory for the 1^st server.

Is max-saved-replicated-journal-size parameter available in any wildfly version? Could find it in HornetQ file present in trunk but doesn't seem to be released.

Is there any way to use ut with jboss7.2.0 by building HornetQ subsystem?

Can HornetQ messaging subsystem be restarted without restarting the whole server?

We are not able to proceed with our HA and cluster configurations due to this issue. It is not feasible to restart server manually on failback in production.

Can you suggest any other solution or workaround?

Regards,

Veena

[jbertram]

I believe you'd need to move to Wildfly to get that specific bit of functionality.  Otherwise you can just run your HornetQ server standalone and configure your applications in JBossAS/Wildfly to connect to them remotely.

[veenaonnet]

Thanks Justin. Have moved to Widfly7.2.0 and using the latest code of HornetQ to get the max-saved-replicated-journal-size parameter.

One query - If the parameter is present in HornetQ and I want it to be configurable through standalone-full-ha.xml, what should be replaced?

I could see the parameter in Hornetq hornetq-configuration.xsd file. How can I use this xsd for standalone-full-ha messaging subsystem?

[jbertram]

To my knowledge there is no such thing as "Wildfly7.2.0".  Wildfly starts at 8.0.0.Alpha1.  See http://wildfly.org/downloads.  In any event, I think you'd need to build it yourself or grab a WildFly nightly build. 

Both JBoss AS7 and Wildfly have their own "messaging" subsystem which has its own schema that isn't directly related to the HornetQ schema.  Any new functionality added in HornetQ (e.g. max-saved-replicated-journal-size) has to be added to the messaging subsystem.

[veenaonnet]

Thanks.

We have taken 7.2.0 jboss code from github and built it.

[jbertram]

We have taken 7.2.0 jboss code from github and built it.

That's not Wildfly.  That's JBoss AS7 before the switch to Wildfly.  I don't think it will have the changes you need to support the new config option.