AMQ Master/Slave Database Restart Results In Multiple Master Brokers

Solution Verified - Updated -

Issue

Using the following JDBC persistence adapter configuration with the default JDBC database locker

<jdbcPersistenceAdapter dataSource="#oracle-ds" lockKeepAlivePeriod="0" maxRows="200" cleanupPeriod="120000" />

it is possible to get two brokers running as master on the same JDBC store.
The key is to set lockKeepAlivePeriod="0", which disables keep alive.

Environment

  • Fuse MQ Enterprise 7.1
  • Fuse ESB Enterprise 7.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.