❗Connexion not closed if the Close() function is called when RabbitMQ is OFF

[alexisfouqueteuroplacer]

We have a scenario that results to a very bad behavior:

• We create an endpoint, add a subscribe channel and a reception callback ✅
  -> We receive the messages from the callback ✅
• The RabbitMQ server is shut down for whatever reason
• Later, the endpoint is closed and "removed" (myEndpoint = null) for an applicative reason
• Later, the RabbitMQ server is started up
  -> We can see the consumer on the queue in the RabbitMQ interface, and the messages are consumed ❌
  -> A Socket.Pool task is still running in the app ❌

This is very bad because the messages are consumed but lost then. And if we create the endpoint back, we have now 2 consumers on the same queue...

We reproduce this scenario each time. And if we just drop the RabbitMQ server shutdown/startup, we don't have the problem.

Versions : CFX SDK 1.5.3 - AMQPNetLite 2.4.4 - RabbitMQ 3.11.1 - Erlang 25.1.1