Clustered qpid broker does not want to start due to damaged store

Solution Verified - Updated -

Issue

A clustered qpid broker shut down due to a hardware problem on disk. The second qpid broker in the cluster continued running and providing service. However an attempt to start the failed broker was not successful due to "BDB exception occurred while initializing store". How to get it running?

Environment

  • MRG Messaging 2

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