[rabbitmq-discuss] Consequences of not ACK-ing

Sat Feb 11 13:59:56 GMT 2012

On Feb 11, 2012, at 1:35 PM, "Bell, Paul M." <pbell at syncsort.com> wrote:

> Specifically, I read that if a consumer doesn't ACK (and assuming no auto-ack), then the broker will NOT deliver another message to that consumer, until it does ACK the previous message

This would have been true if you had a QoS with a prefetch count of 1, but by default it will deliver as many messages as it can while you read from the socket   . If you have a prefetch count of 4 it will deliver 4 unacked msgs at a time and so on.

> .