Clarify what occurs when basic.ack is sent for a message received by a consumer in 'no-ack' mode

[zbentley]

trafficstars

Minor documentation omission in the AMQP protocol pages.

This might be a documentation omission for rabbitmq-server itself, I am not sure.

The protocol documentation (either quick reference or full reference) should clarify what behavior occurs when a basic.ack is sent for a message received by a consumer that is operating in no-ack mode.

Does this cause a failure? Is the basic.ack ignored? Even if this behavior is explicitly undefined/untrustable, a note should be added indicating that this is the case.

[michaelklishin]

It results in a channel-level exception saying that a delivery tag isn't known to the channel.

Both protocol documents aren't updated any more and I don't think this is something that belongs to the errata page. I suspect we need a separate documentation page for consumer confirms.

[zbentley]

That seems reasonable, thanks for the quick reply!

I've observed the failures on the versions of RabbitMQ I've used. I was mostly after documentation so that I and others can be a little more sure that the behavior will not switch from "error" to "undefined" in a future version.