[QPID-8086] [Broker-J] Create tool to permit recovery from QPID-8066

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-6.1.6, qpid-java-broker-7.0.1
• Component/s: Broker-J
• Assignee: Keith Wall
• Reporter: Keith Wall
• Created: 24/Jan/18 15:36
• Updated: 02/Oct/19 19:22
• Resolved: 30/Jan/18 12:26

Description

Defect QPID-8066 has the potential to leave the Broker in a state where it cannot be restarted. The recovery phase, on encountering the orphan records, throws an exception and this puts the virtualhost into an ERROR state.  There is no facility in Broker-J to recover from this short of recreation of the virtualhost.

If the configuration store is backed by JDBC, then a workaround is to connect to the database and remove the offending rows.   Unfortunately if the virtualhost is backed by BDB (for configuration) or BDB HA, the user has no convenient way to recover the situation.  BDB JE has no command line interface so a Java program would have to be written with knowledge of the store's structure.  The HA case is further complicated by the fact that sufficient nodes would have to be available to provide quorum within the group.

Issue Links

• is related to: QPID-8066 [Broker-J] Virtual host logger rules are left over in configuration store after deletion of virtual host logger on provided virtual host causing virtualhost restart failure
• relates to: QPID-8068 [JMS AMQP 0-x] Change of noLocal on re-subscription of durable subscriber does not re-create the subscription