Multiple reject/ack call should throw precondition failed

[shark300]

I tried to deploy our application to staging environment and I assumed it will work without exception/warning because I have tested some error cases in ITs regarding to message rejecting too. Unfortunately, I have got some warning:

"Channel shutdown: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - unknown delivery tag 1, class-id=60, method-id=80)"

The root cause of this warning is that:

"Client Errors: Double Acking and Unknown Tags
Should a client acknowledge the same delivery tag more than once, RabbitMQ will result a channel error such as PRECONDITION_FAILED - unknown delivery tag 100. The same channel exception will be thrown if an unknown delivery tag is used." https://www.rabbitmq.com/confirms.html

I've tried some combination of rejecting but I can't get a warning in this use cases:

      channel.basicReject(original.getMessageProperties().getDeliveryTag(), false); // successful
      channel.basicReject(original.getMessageProperties().getDeliveryTag(), false); // already rejected, should have a warning

      channel.basicReject(original.getMessageProperties().getDeliveryTag(), false); // successful
      channel.basicAck(original.getEnvelope().getDeliveryTag(), false); // already rejected, should have a warning

      channel.basicAck(original.getEnvelope().getDeliveryTag(), false); // successful
      channel.basicReject(original.getMessageProperties().getDeliveryTag(), false); // already acknowledged, should have a warning

      channel.basicAck(original.getEnvelope().getDeliveryTag(), false); // successful
      channel.basicAck(original.getEnvelope().getDeliveryTag(), false); // already acknowledged, should have a warning

      channel.basicReject(15, false); // unknown tag, should have a warning too

      channel.basicAck(15, false); // unknown tag, should have a warning too

[ledoyen]

Hi, thanks for reporting this.

A fix will be supplied as soon as I get the time to do it.

It is the perfect opportunity to setup a new kind of test were the test is played twice with a real rabbitmq and with the mock to assert that the behavior is consistent.