This behaviour cannot be disabled, but you can set MaxDeliver圜ount to a very large number. When Deliver圜ount exceeds MaxDeliver圜ount, the message is moved to the DLQ, specifying the ‘MaxDeliver圜ountExceeded’ reason code. Header Size Exceeded – Maximum header size: 64 KB.Here we can drill down the reasons into two ways: The failed delivery can also be caused by a few other reasons such as network failures, a deleted queue, a full queue, authentication failure, or a failure to deliver on time. If in case the message doesn’t have a mandatory parameter or some value is incorrect, then the message will end up in the dead-letter queue after the max delivery count is attained. For instance, Redis or SQL connection issues may often happen. This could be one of the foremost and time after time reasons where the services that reply on message delivery may go down for a short period. Most of the time we could notice that the message fails to reach the receivers due to the following reasons So, any message that resides in the dead-letter queue is called a dead-lettered message.īefore investigating the best way to monitor and reprocess Service Bus messages efficiently, let us quickly hop in and understand the reasons behind why an active message get dead-lettered. The purpose of the dead-letter queue is to hold messages that cannot be delivered to any receiver, or messages that could not be processed. Azure Service Bus queues and topic subscriptions provide a secondary sub-queue, called a dead-letter queue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |