Repository navigation
RabbitMQ AMQP 1.0 should not set an empty exchange by default - #52305
Merged
snicoll merged 2 commits intoOct 23, 2026
Merged
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
snicoll
added
type: bug
See spring-projectsgh-52305 Signed-off-by: Daler Azimov <daler445@gmail.com>
snicoll
changed the title
snicoll
force-pushed
the
fix/amqp-rabbit-empty-exchange
branch
from
October 23, 2026 13:41
c414eea to
09397cc
Compare
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
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.
RabbitMQ AMQP 1.0 auto configuration sets the empty exchange on RabbitAmqpTemplate by default. unlike the AMQP 0.9.1 template, the AMQP 1.0 template does not support the default exchange
this also prevents
setQueue()from working when configured through a RabbitAmqpTemplateCustomizer