Disallow multiple consumers on one volatile queue #14528
Merged
Conversation
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
There can be at most one consumer per volatile queue instance. This consumer must also have attached on the same channel/session as the creator of the queue. Prior to this commit, it was possible for clients on other connections or sessions to attach a receiving link to an existing volatile queue name, even though no messages would be delivered. It's better for RabbitMQ to directly refuse the link at attach time.
ansd
added a commit
that referenced
this pull request
Sep 12, 2025
Disallow multiple consumers on one volatile queue (backport #14528)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There can be at most one consumer per volatile queue instance. This consumer must also have attached on the same channel/session as the creator of the queue.
Prior to this commit, it was possible for clients on other connections or sessions to attach a receiving link to an existing volatile queue name, even though no messages would be delivered.
It's better for RabbitMQ to directly refuse the link at attach time.