Repository navigation
Harden Article Work channel recovery after RabbitMQ failures - #238
Merged
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
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.
Summary
Fixes #193 by recovering Article Work consumers and response publishers when their RabbitMQ channels fail independently of the underlying AMQP connection.
Previously, a consumer could remain marked
Runningafter its channel closed or the broker cancelled its consumer. Similarly, a failed response-publisher channel could remain installed indefinitely, causing subsequent publishes to fail repeatedly.Changes
Consumer recovery
IRabbitMqManualAckChannel.Runningstate.Publisher recovery
Tests and reliability
Validation
dotnet format --verify-no-changes: passedRecovery behaviour
Channel-level failures are handled independently of connection-level failures. A healthy AMQP connection is retained, while genuine connection failures continue through the existing connection-recovery mechanism.