Fix exchange naming with FromHandlerType routing#2428
Merged
jeremydmiller merged 1 commit intomainfrom Apr 3, 2026
Merged
Conversation
When using UseConventionalRouting(NamingSource.FromHandlerType), exchanges were incorrectly named after the handler type instead of the message type. This caused a mismatch between sender exchanges (always message-type-named) and listener exchanges, breaking message routing. Now the queue is named after the handler type while the exchange correctly uses the message type. Closes #2397 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 7, 2026
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
1 participant
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.
Summary
UseConventionalRouting(NamingSource.FromHandlerType), exchanges were incorrectly named after the handler type instead of the message type, causing sender/listener exchange mismatchMessageRoutingConventionto pass the original message type through toApplyListenerRoutingDefaultsso queues use handler type names while exchanges use message type namesTest plan
when_using_handler_type_namingtests pass against live RabbitMQexchange_should_be_named_after_message_type_not_handler_typeverifies exchange uses message typequeue_should_be_bound_to_message_type_exchangeverifies queue binds to message-type exchangeCloses #2397
🤖 Generated with Claude Code