#Ezbot auto queue how to#
You could specify the Maximum Delivery Count between 483647.ĭo you want us to help set up and showcase how to monitor and handle dead-letter messages in a smarter way? Talk to us 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:
#Ezbot auto queue full#
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
0 kommentar(er)
