lapin icon indicating copy to clipboard operation
lapin copied to clipboard

Reconnect on shutting down AMQP service

Open mjanssen opened this issue 9 months ago • 3 comments

Hi,

We have experienced some issues with one of our providers killing their services every once in a while, which results in Lapin to stop consuming messages.

We have an implementation based on the reconnect example, which functions when Lapin can't find the queue name for example, but nothing happens when the service is killed.

I have a test setup that connects to a local instance of RabbitMQ, which I can terminate. I can connect to a queue and receive messages when I publish a message on the queue. However, when I kill the container, nothing happens in the Lapin connection and it still waits for messages (line 52 of the example).

When I boot RabbitMQ again and publish a message on the same queue, the message is not received in the Lapin message loop.

Any clue how to fix this issue?

mjanssen avatar Sep 20 '23 16:09 mjanssen