We’ve just released NServiceBus.RabbitMQ 5.0.1 and 4.4.2. These releases remove a race condition that can prevent endpoints from successfully processing messages. This race condition can be observed when a connection to the broker goes through the auto-recovery process.
- #484 Endpoint getting stuck with "System.Exception: Failed to add " in the logs
How to know if you are affected
You are affected if you are using version 4.x or 5.x of the transport. Version 3.x is not affected by this problem.
Processing of some of the incoming messages fails. In extreme cases, all messages are stuck in the input queue. The following entries are logged by the endpoint:
System.Exception: Failed to add at
A process restart is necessary to get the endpoint unstuck.
Should you upgrade immediately
All users experiencing the symptoms should upgrade immediately.
Where to get it
You can download the updated version and see the full release notes here:
The team in Particular
Please read our release policy for more details.