Automatic local fanout for separated handlers (GH-2198)#2199
Merged
jeremydmiller merged 2 commits intomainfrom Feb 16, 2026
Merged
Automatic local fanout for separated handlers (GH-2198)#2199jeremydmiller merged 2 commits intomainfrom
jeremydmiller merged 2 commits intomainfrom
Conversation
…GH-2198) When using MultipleHandlerBehavior.Separated with external brokers, messages now automatically fan out to all local handler queues instead of throwing NoHandlerForEndpointException. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…monolith tutorial Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Feb 17, 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
MultipleHandlerBehavior.Separatedwith external broker endpoints (RabbitMQ, Kafka, Azure Service Bus, etc.), messages now automatically fan out to all separated local handler queues instead of throwingNoHandlerForEndpointExceptionFanoutMessageHandler<T>that receives the message at the external endpoint and re-publishes it to each local queue, preserving envelope headersTest plan
sticky_message_handlersCoreTests still pass (sending to an unmatched local queue still throws the expected exception)Bug_1684_separated_handlers_and_conventional_routingtest still passes🤖 Generated with Claude Code