[
https://issues.apache.org/jira/browse/QPID-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke resolved QPID-4423.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.19
Fixed in r1406809 Nov 7, 2012
> C++ Broker Dynamic and static federation should not declare existing queues
> ---------------------------------------------------------------------------
>
> Key: QPID-4423
> URL: https://issues.apache.org/jira/browse/QPID-4423
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.18
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
> Fix For: 0.19
>
>
> When configuring either a dynamic or static federated link, it is possible to
> provide the name of an existing queue to utilize. The issue is that 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. When the destination broker creates a queue
> it will use default queue settings (i.e. trace/exclude, reject policy,
> default size limits) and not the desired configured settings that the queue
> will have when created properly on the source broker.
> The proposal to fix this issue is if a queue name was provided during a
> bridge declaration then the broker should not attempt to declare the queue.
> When no name is provided then the broker may go ahead and declare an
> exclusive queue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
