[rabbitmq-discuss] Retrying messages that failed to process

[Jason McIntosh]

If you're in Java and using the spring frameworks, there's retry handling
support.
https://github.com/jamescarr/spring-amqp-extras
You could probably implement something similar - on an "exception" publish
to an error queue that has priority?  Just an idea :)
Jason


On Wed, Jul 17, 2013 at 9:12 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 18/07/13 00:54, Laing, Michael wrote:
>
>> AFIK, however, the rejected/nacked messages is queued as if it were new,
>> but with the redeliver flag set, AND any consumer may receive them,
>> including the one which rejected/nacked them. Of course if you have
>> multiple consumers on a queue, the rabbit will round-robin.
>>
>> But, the rejected/nacked message does not go to the 'front' of the queue
>> as you desired (again AFAIK).
>>
>
> Actually, since RabbitMQ 2.7.0 messages get requeued in publication order.
> See http://www.rabbitmq.com/**semantics.html#ordering<http://www.rabbitmq.com/semantics.html#ordering>for the details.
>
> Matthias.
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>



-- 
Jason McIntosh
http://mcintosh.poetshome.com/blog/
573-424-7612
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130723/13fe9903/attachment.htm>