-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Host] Abandon/dead letter message #356
Comments
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Yes, we could add this as an asb transport specific feature. Perhaps even unify across all transports (but not sure about if it's worth unifying). |
What would be good is also gave the ability to set application properties (headers) from the error handler or consumer when message is abandoned on the asb transports. This helps to convey partially completed work and have it available for the next message retry. |
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
Signed-off-by: Richard Pringle <richardpringle@gmail.com>
SMB does not provide an out of the box way to dead letter messages for the transports that support it. It is currently possible for RabbitMQ through a nack in a
IConsumerErrorHandler
, but not for Azure Service Bus.ASB messages that throw an exception will be retried n times before finally being sent to the DLQ.
If an exception can be determined to be non-transient (and therefore will not be resolved in a subsequent execution), it would be beneficial to send the message to the DLQ immediately.
The text was updated successfully, but these errors were encountered: