Show Table of Contents
1.4.3. Ambiguous Addresses in AMQP 1.0
When a client uses an ambiguous address over AMQP 1.0 - where both a queue and an exchange of the same name exist and the client does not explicitly specify the node type - the queue is used by default. No exception or warning is printed out, and the client is not informed in any way of the ambiguity. A warning is logged by the broker when the node matches both a queue and an exchange and no specific type is specified.
When using an AMQP 0-10 client, in contrast, the following exception is reported: "
Ambiguous address, please specify queue or topic as node type".
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.