HornetQ shared store live/backup configuration does not failover correctly.

Solution Verified - Updated -

Issue

  • Two HornetQ instances are configured as a live/backup pair with shared storage using GFS2.
    The logs show that the backup instance becomes active immediately on start up instead of waiting for the live instance to stop.
2013-10-30 19:02:37,927 INFO  [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=4f23b5c4-3c05-11e3-9dbc-51b183d8fb28) HQ221109: HornetQ Backup Server version 2.3.1.Final (BZ1017943, 123) [4f23b5c4-3c05-11e3-9dbc-51b183d8fb28] started, waiting live to fail before it gets active
...
2013-10-30 19:02:37,927 DEBUG [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=4f23b5c4-3c05-11e3-9dbc-51b183d8fb28) acquired live node lock state = L
...
2013-10-30 19:02:37,975 INFO  [org.hornetq.core.server] (Thread-0 (HornetQ-server-HornetQServerImpl::serverUUID=4f23b5c4-3c05-11e3-9dbc-51b183d8fb28-359279779)) HQ221031: backup announced
...
2013-10-30 19:02:40,187 INFO  [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=4f23b5c4-3c05-11e3-9dbc-51b183d8fb28) HQ221010: Backup Server is now live

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
    • GFS2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content