Cause: If a queue name is provided during the creation of a federated link then the destination broker may declare the queue if it does not exist.
Consequence: There is a race condition during a broker restart. A link request may be received before the queue in question has been recovered. If the queue is recovered through normal broker configuration then it may have various non-default properties. However if the queue is created through the link request then the queue will be created with default properties and the subsequent queue recovery operation will fail.
Fix: Do not create queues that are named in federated link requests.
Result: During restart. as resources are being recreated, the destination broker will eventually create the queue with the correct properties. Federation link requests that happen before the queue is created will fail but after the queue is created then the retried link requests will succeed and the destination queue will have the correct properties.