[0.15] Set AMQP strategy to modified-failed #2120
Merged
Conversation
This file contains 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
This strategy keeps accepting new messages even if one failed, therefore without closing the connections at first failure. Signed-off-by: Andrea Lamparelli <[email protected]>
lampajr
approved these changes
Oct 23, 2024
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.
Backport: #2113
This strategy keeps accepting new messages even if one failed, therefore without closing the connections at first failure.
Fixes Issue
Fixes #2103
Changes proposed
The default messaging fail strategy is
failwhich stops the application from receiving messages at first failure, as stated here https://quarkus.io/guides/amqp-reference#failure-managementmodified-failedwhich put the failed message in DLQ but keeps processing all the others without disconnecting the connectionsCheck List (Check all the applicable boxes)