Conversation
## What? 1. This commit adds the name of the queue that rejected a message as well as the reason why the message was rejected in the Rejected outcome for AMQP 1.0. 2. For MQTT 5.0 publishers, the reason is provided in the PUBACK packet. ## Why? It may be helpful for publishers to know which queue out of multilple target queues rejected the message. One such use case is described in #1443 It may also be helpful to know for publishers whether the given target queue rejected the message because its maximum queue length was reached or because the target queue happens to be unavailable. ## How? RabbitMQ will include the UTF-8 encoded queue name (rather than an AMQP address) as well as the reason in the `info` field of the Rejected outcome's `error` field: * `queue: <queue name>` * `reason: maxlen | unavailable` For MQTT 5.0, if the queue length limit is exceeded, RabbitMQ will return the reason code for `Quota exceeded` to the publisher.
Collaborator
|
For STOMP, we can add these values via AMQP 0-9-1 would require a protocol extension similarly to how |
Member
Author
The Instead, the target queue and reason why RabbitMQ rejected a message would need to be included in the STOMP |
ansd
added a commit
that referenced
this pull request
Dec 9, 2025
### What? This commit is a follow-up to #15075 setting the `description` field of the AMQP `error` if RabbitMQ rejects a message. ### Why? Client libs can then just pass this error description string to client apps, which in turn could optionally log that message.
ansd
added a commit
that referenced
this pull request
Dec 9, 2025
### What? This commit is a follow-up to #15075 setting the `description` field of the AMQP `error` if RabbitMQ rejects a message. ### Why? Client libs can then just pass this error description string to client apps, which in turn could optionally log that message.
ansd
added a commit
that referenced
this pull request
Dec 10, 2025
This is a follow up to #15075 For maximum queue length exceeded use more appropriate error condition `resource-limit-exceeded` (instead of `precondition-failed`).
ansd
added a commit
that referenced
this pull request
Dec 10, 2025
This is a follow up to #15075 For maximum queue length exceeded use more appropriate error condition `resource-limit-exceeded` (instead of `precondition-failed`).
michaelklishin
pushed a commit
that referenced
this pull request
Dec 11, 2025
### What? This commit is a follow-up to #15075 setting the `description` field of the AMQP `error` if RabbitMQ rejects a message. ### Why? Client libs can then just pass this error description string to client apps, which in turn could optionally log that message.
michaelklishin
pushed a commit
that referenced
this pull request
Dec 11, 2025
This is a follow up to #15075 For maximum queue length exceeded use more appropriate error condition `resource-limit-exceeded` (instead of `precondition-failed`).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Why?
It may be helpful for publishers to know which queue out of multilple target queues rejected the message. One such use case is described in #1443 It may also be helpful to know for publishers whether the given target queue rejected the message because its maximum queue length was reached or because the target queue happens to be unavailable.
How?
RabbitMQ will include the UTF-8 encoded queue name (rather than an AMQP address) as well as the reason in the
infofield of the Rejected outcome'serrorfield:queue: <queue name>reason: maxlen | unavailableFor MQTT 5.0, if the queue length limit is exceeded, RabbitMQ will return the reason code for
Quota exceededto the publisher.Docs PR: rabbitmq/rabbitmq-website#2413