Rabbitmq: Unacked message not going away after broker restart
问题 We have observed the following behavior of RabbitMQ and are trying to understand if it is correct and how to resolve it. Scenario: A (persistent) message is delivered into a durable queue The (single) Consumer (Spring-AMQP) takes the message and starts processing => Message goes from READY to UNACK Now the broker is shut down => Client correctly reports "Channel shutdown" The consumer finishes the processing, but can not acknowledge the message as the broker is still down Broker is started