<div dir="ltr">Great! thanks, this was quite useful.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 3, 2013 at 3:07 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 03/05/13 10:15, Ashok Anand wrote:<br>
> 1) what should I use to go through all messages in the queue,<br>
> currently, "./rabbitmqadmin get queue=qname requeue=true" gives only<br>
> head. does any such interface exists currently to get list of all<br>
> messages in the queue?<br>
<br>
</div>You can retrieve more than one message by supplying the "count" parameter.<br>
<br>
I would recommend using a client library and writing the software to<br>
accomplish your goals. For your use-case b) all the operations (message<br>
retrieval, selective acknowledgement and requeueing) will need to be<br>
performed on the same channel, which precludes composing a sequence with<br>
multiple invocations of a commandline utility.<br>
<div class="im"><br>
> 2) Just the re-delivery flag is set, right? so the consume should not<br>
> assume that it is a retrial of the same message?<br>
<br>
</div>The consumer can't distinguish between a message that was requeued due<br>
to exceptional circumstances (e.g. network disconnection while a message<br>
was unacknowledged) and a message that was explicitly requeued.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
<br>
-Emile<br>
<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>