[rabbitmq-discuss] Prefetch fields in management UI

Ben Hood 0x6e6562 at gmail.com
Wed Apr 23 00:21:56 BST 2014

On Tue, Apr 22, 2014 at 7:19 PM, Ben Hood <0x6e6562 at gmail.com> wrote:
> I have a feeling that this might be a client issue. The screenshots I
> sent were made using an the Go amqp driver - the official Java client
> doesn't seem to have this issue. Sorry about the noise.

Turns out this issue is reproducible with the official Java client,
but it might just be due to lack of RTFM. So qos does not appear to
take effect if the command is submitted after the call to subscribe to
a queue, with in the context of a single channel. So to fix this
issue, all I needed to do is to make sure that setting the prefetch
happens before subscribing to a queue. I never realized that egress
qos is order dependent - I had just assumed that that it is a
changeable value within the context of the limiter.

What puzzled me is that the same app running against 3.2.4 does not
(anecdotally) seem to care as much about the command order as the
current release. I probably need to re-read the documentation.

More information about the rabbitmq-discuss mailing list