Add support for dead letter exchange and queue arguments in AMQP #691
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.
Pull Request type
Changes in this PR
Enhanced AMQPSettings to support additional RabbitMQ queue arguments through URI parameters.
New URI Parameters:
Example usage:
Problem
When workflows are triggered via Event Handlers sourced from RabbitMQ, and the workflow initiation fails due to backend database issues, the incoming message is nacked using
basic.nackwithrequeue=false. As a result, the message is not requeued to the original queue and is expected to be routed to a Dead Letter Exchange (DLX). However, since the DLX configuration is currently not in place, the message is ultimately discarded.Solution
By introducing new parameters for Dead Letter Exchange (DLX) configuration that enable queues to use DLX settings, along with additional arguments for message expiration (TTL) and maximum queue length, all of which are optional.