[Host.RabbitMQ] RabbitMQ server restart causes SlimMessageBus to lose…

[zarusz]

Issue

When the RabbitMQ connection is recovered by RabbitMqChannelManager, it creates a new channel and provisions topology, but the existing consumers that were created in OnStart() are not being recreated. The AsyncEventingBasicConsumer instances are still attached to the old, closed channel.

Here's the issue:

1. AbstractRabbitMqConsumer.OnStart() creates an AsyncEventingBasicConsumer and calls BasicConsume() on the channel
2. When RabbitMQ restarts, RabbitMqChannelManager detects the connection loss and creates a new connection and channel
3. However, the consumers are never notified about this and don't re-register themselves with the new channel
4. Messages accumulate in the queue because there are no active consumers

Solution

The fix requires implementing a mechanism to notify consumers when the channel is recovered, so they can re-register themselves.

Fixes #436

[sonarqubecloud]

Quality Gate failed

Failed conditions
59.7% Coverage on New Code (required ≥ 75%)

See analysis details on SonarQube Cloud