Description of problem: When configuring either a dynamic or static federated link, it is possible to provide the name of an existing queue to utilize. The destination broker of the federated route will attempt to declare the queue regardless of whether or not it should be using an existing queue. This can result in a race condition if the pre-existing queue is not yet available on the source broker, so the destination broker creates a queue with default queue settings (i.e. trace/exclude, reject policy, default size limits). If a queue name was provided, the broker should not attempt to declare the queue. Version-Release number of selected component (if applicable): Qpid 0.18-6 How reproducible: 100% Steps to Reproduce: 1. Create a dynamic or static federation route, providing a queue name Actual results: The queue is declared on the source broker. Expected results: The queue should be be declared on the source broker. Additional info:
Created attachment 638952 [details] Quick patch to avoid declaring an existing queue
Patch for review at: https://reviews.apache.org/r/7901/
Reviewers Conway and Ross need to understand better what the underlying problem is. Can you describe in more detail the use case that the patch fixes?
Fixed upstream at r1406809
Tested on RHEL5.9 and RHEL6.4. This issue has been fixed. Packages used for testing: qpid-cpp-0.18-14 -> VERIFIED