thanks... more testing tomorrow<br><br><div class="gmail_quote">2009/11/18 Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, Nov 18, 2009 at 05:18:53PM +0000, Matthew Sackman wrote:<br>
> That's odd. However, you're really much much better off using<br>
> queue.declare to redeclare the existing queue - the declare-ok that you<br>
> get back contains the number of messages in the queue. This is a much<br>
> neater strategy than below. I would recommend you switch to using this<br>
> and repeat your test.<br>
<br>
</div>What's actually wrong with what you were doing is that the rabbitmqctl<br>
list_queues contains both the ready messages and the unack'd msgs (as<br>
well as uncommitted msgs). Thus if your consumers aren't acking msgs<br>
quickly enough (and have an unbounded qos setting) then it will appear<br>
that they're not keeping up. Use:<br>
<br>
rabbitmqctl list_queues name messages_ready messages_unacknowledged<br>
<div><div></div><div class="h5"><br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>