Multi-ack can block consumption when rate limitation is enabled

[acogoluegnes]

To reproduce:

# fill up a queue
perf-test -x 1 -y 0 -c 3000 -C 100000 -r 10000 -qq -u qq
# consume... or not
perf-test -x 0 -y 1 -A 1000 -q 1000 -R 10000 -qq -u qq

The consumer stops at some point, because it does not ack at the appropriate time and the number of un-acked messages reaches the QoS.

rabbitmq-perf-test/src/main/java/com/rabbitmq/perf/Consumer.java

Line 268 in 94edf4d

state.setMsgCount(0);

rabbitmq-perf-test/src/main/java/com/rabbitmq/perf/Consumer.java

Line 285 in 94edf4d

} else if (currentMessageCount % multiAckEvery == 0) {

[acogoluegnes]

There should be 3 message counts:

• one to choose when to ack or commit (to be reset when recovery takes place)
• one for rate limitation (because it needs to be reset sometimes)
• one for absolute count (used to stop the consumer when it reaches its limit)