JBoss A-MQ; how to use persistence store locking for master/slave in a Fabric

Solution Verified - Updated -

Issue

  • In a Fabric, master/slave brokers are coordinated using a Zookeeper lock. If the Fabric ensemble is not available (e.g losing the ensemble quorum) the master/slave broker pair will become unavailable. How can we set up a master/slave broker pair that does not rely on fabric for its locking?

Environment

  • JBoss A-MQ 6.x

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