A-MQ Broker fails to start its Scheduler service upon restart and enters slave mode

Solution Verified - Updated -

Issue

If the A-MQ broker gets stopped while starting up (as part of a bundle refresh during Fabric container start-up) it may raise a BrokerStoppedException and it may fail to properly shut down the Scheduler's KahaDB instance.

Upon broker restart (again, as part of bundle refresh during container start-up) the broker will fail start up fully as the Scheduler KahaDB instance is still locked.
The broker will raise
Database data/mybroker/mybroker/scheduler/lock is locked by another server. This broker is now in slave mode waiting a lock to be acquired
and will fail to start up fully. It will not open its transport connector and hence cannot be contacted by clients.

Environment

  • Red Hat Fuse 6.3
  • Red Hat A-MQ 6.3
  • Fabric mode
  • Broker Scheduler support enabled

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