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

["Alex Rudyy (JIRA)" <ji...@apache.org>]

Alex Rudyy created QPID-8229:
--------------------------------

             Summary: [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used
                 Key: QPID-8229
                 URL: https://issues.apache.org/jira/browse/QPID-8229
             Project: Qpid
          Issue Type: Task
          Components: Broker-J
    Affects Versions: qpid-java-6.1.5, qpid-java-6.1.4, qpid-java-6.1.3, qpid-java-6.1.2, qpid-java-6.1, qpid-java-6.1.6
            Reporter: Alex Rudyy
             Fix For: qpid-java-6.1.7


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:
{noformat}
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.
{noformat}

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.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org