[rabbitmq-discuss] Messages BasicReject-ed or BasicNack-ed are back in the queue after restarting RabbitMQ service

[JohanKlijn]

We are using RabbitMQ 2.8.1 using C#. We have a queue with durable messages.
When we Acknowledge a message, channel.BasicAck(deliveryTag, false), and
restart the RabbitMQ service the message acknowledge is will not appear any
more in the queue, as expected.

Now when we negative acknowledge a message, like this:

channel.BasicNack(deliveryTag, false, false);
or 
channel.BasicReject(deliveryTag, false);

and restart the service the messages negative acknowledged are back.
When I look at the status of the queue before the restart using:
rabbitmqctl list_queues name messages_ready messages_unacknowledged
There are no messages to be acknowledge and the NumberOfMessages =
NumberOfMessageBeforeNegAck – NegAckMessages. And after the restart the
NumberOfMessages = NumberOfMessageBeforeNegAck.




--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Messages-BasicReject-ed-or-BasicNack-ed-are-back-in-the-queue-after-restarting-RabbitMQ-service-tp31180.html
Sent from the RabbitMQ mailing list archive at Nabble.com.