[QPID-8229] [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: qpid-java-6.1.6, qpid-java-6.1, qpid-java-6.1.2, qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.1.5
• Fix Version/s: qpid-java-6.1.7
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 20/Aug/18 13:22
• Updated: 03/Sep/18 00:13
• Resolved: 30/Aug/18 07:56

Description

Queue bindings can be left behind in BDB/DERBY/JDBC configuration stores on queue deletion. When virtual host with a deleted queue and orphaned binding is restarted, the Virtual Host startup fails with error "422 - No parent of class Queue found.". The following warning is reported into the logs:

WARN  [HttpManagement-HTTP-379] (o.a.q.s.m.p.s.r.RestServlet) - IllegalArgumentException processing request http://localhost:8080/api/latest/virtualhost/tmp2/tmp2 from user '[/0:0:0:0:0:0:0:1:61279, admin]': No parent of class Queue found.

The work-around for the issue would a deletion of all queue bindings prior queue deletion. There is no work around which would allow to delete orphaned bindings and recover Virtual Host configuration apart from changing store data directly which is not feasible in case of BDB.

Issue Links

• is related to: QPID-7933 [Java Broker] Changes made to existing durable children of virtualhost not recorded to the configuration store after a virtualhost restart