EasyNetQ icon indicating copy to clipboard operation
EasyNetQ copied to clipboard

Subscriptions do not re-establish after auto-deletion

Open bradley-dotnet opened this issue 9 years ago • 1 comments

On version 54.3.424 using auto-deletion, the following steps have an issue:

  1. Start RabbitMQ
  2. Connect to the broker, start publishing items
  3. Subscribe to the broker with Auto-Delete set to "True"
  4. Stop the RabbitMQ service
  5. Restart the RabbitMQ service

The queues auto-delete and never come back. The connections seem to be re-established as the management console reports the correct number and the subscriber stops reporting disconnected events.

If the subscriber restarts (re-establishing the subscription in the process) everything works fine. If non-auto deleting queues are used, everything works as well. Publishers do not seem to run into this problem either.

The logs indicate a "consume failed" for every queue that was being subscribed to.

bradley-dotnet avatar Apr 26 '16 21:04 bradley-dotnet

It's kind of normal. The solution that I do is create a wrapper on the bus, when subscribe auto deletion, it subscribe through the wrapper. Wrapper stores all subscription information and subscribe bus reconnected event.

stevenxi avatar Nov 06 '16 23:11 stevenxi