We have an issue when an error occurs on consumer side: we saw that the process tracks the error count only InMemory (InMemErrorTracker on Rebus) so when a process runs on a single machine or a cluster and the process crush, the errors count goes lost.
In this way, using the AzureServiceBus, we are trying to retry to process that message up to MAX (that we saw is 100) instead of stopping after few attempts.
Do you accept a PR in which we put the MaxDeliveryCount property settable from outside so we can change it? in this way we can go in dead letter and stop retrying to process that message.
Hi!
We have an issue when an error occurs on consumer side: we saw that the process tracks the error count only InMemory (InMemErrorTracker on Rebus) so when a process runs on a single machine or a cluster and the process crush, the errors count goes lost. In this way, using the AzureServiceBus, we are trying to retry to process that message up to MAX (that we saw is 100) instead of stopping after few attempts.
Do you accept a PR in which we put the MaxDeliveryCount property settable from outside so we can change it? in this way we can go in dead letter and stop retrying to process that message.