eef470df37
## What? Refuse or detach the link instead of ending the session for many link-level errors, including the following: * Source queue or target exchange doesn't exist during attach * Trying to consume from an exclusive queue on a different connection * Delivery of message to a target queue fails * Wrong delivery-id * Wrong settled flag * Queue declaration fails for dynamic queues * Publishing to internal exchange ## Why? Because many errors are scoped to a single terminus, detaching just that link preserves the rest of the session’s links - avoiding needless disruption of other traffic. AMQP 1.0’s error model is hierarchical; RabbitMQ should escalate to ending the session only for session-level faults or if the client keeps using a destroyed link. ## How? Refuse link as per figure 2.33 |
||
|---|---|---|
| .. | ||
| system_SUITE_data/conf | ||
| activemq_ct_helpers.erl | ||
| mock_server.erl | ||
| msg_SUITE.erl | ||
| system_SUITE.erl | ||