Created attachment 405992 [details] reproduces the bug. Description of problem: Deleting a queue binding in a federation may resulting in stale bindings on the federation brige links. See upstream jira for a repo case: https://issues.apache.org/jira/browse/QPID-2499 Version-Release number of selected component (if applicable): trunk as of Revision: 933254 How reproducible: 100% Steps to Reproduce: See attached script. Actual results: superfluous binding present on intermediate broker Expected results: binding should be cleaned up. Additional info:
Fixed in revision 1058747. Federated binds and unbinds need to know which federation origins are associated with the bindings for each queue. When origins are added or deleted, the corresponding bindings need to be propagated. fedBindings[queueName] now contains the origins associated with a given queue.
verified on both rhel5 and rhel6 / i386/x86_64 rpm -qa | grep qpid | sort -u python-qpid-0.10-1.el6.noarch python-qpid-qmf-0.10-6.el6.x86_64 qpid-cpp-client-0.10-3.el6.x86_64 qpid-cpp-client-devel-0.10-3.el6.x86_64 qpid-cpp-client-devel-docs-0.10-3.el6.noarch qpid-cpp-client-rdma-0.10-3.el6.x86_64 qpid-cpp-client-ssl-0.10-3.el6.x86_64 qpid-cpp-server-0.10-3.el6.x86_64 qpid-cpp-server-cluster-0.10-3.el6.x86_64 qpid-cpp-server-devel-0.10-3.el6.x86_64 qpid-cpp-server-rdma-0.10-3.el6.x86_64 qpid-cpp-server-ssl-0.10-3.el6.x86_64 qpid-cpp-server-store-0.10-3.el6.x86_64 qpid-cpp-server-xml-0.10-3.el6.x86_64 qpid-java-client-0.10-4.el6.noarch qpid-java-common-0.10-4.el6.noarch qpid-java-example-0.10-4.el6.noarch qpid-java-jca-0.10-4.el6.noarch qpid-qmf-0.10-6.el6.x86_64 qpid-qmf-devel-0.10-6.el6.x86_64 qpid-tests-0.10-1.el6.noarch qpid-tools-0.10-3.el6.noarch rh-qpid-cpp-tests-0.10-3.el6.x86_64 ruby-qpid-qmf-0.10-6.el6.x86_64 -->VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0890.html
*** Bug 675303 has been marked as a duplicate of this bug. ***