RabbitMQ 4.0 has a default delivery limit that can cause message loss

Hi everyone,

We’ve been tracking the release of RabbitMQ 4.0, and there is a specific change that we want to call out that can potentially cause message loss.

If you are using quorum queues for your endpoints, the change to the broker’s default delivery limit means that a message could be lost if the endpoint’s immediate retry attempts have been configured to be higher than the new default delivery limit of 20.

If a message fails too many times, the newly enforced default delivery limit means that a message would be discarded by the broker before NServiceBus could attempt a delayed retry.

We are working on a new version of the RabbitMQ transport that is aware of this default delivery limit change and will ensure that the broker is configured in a way that is safe.

If you have already upgraded to RabbitMQ 4.0, we recommend ensuring that that the number of immediate retry attempts are configured to be lower than the new default delivery limit of 20.

If you need help to ensure that your messages will stay safe, don’t hesitate to reach out to support.

With thanks,
The team in Particular