hazard in QoS fixed

It turns out that time between consume and basic.qos is enough for the server to hammer you into oblivion if sufficient messages are enqueued.

"You declare no Qos? Ok, have these 50 thousand messages at once."