[rabbitmq-discuss] requeue problem with rabbitmq version 2.8.1

Tue Apr 10 11:17:51 BST 2012

Hi Ruben,

On 05/04/12 19:46, Ruben Rotteveel wrote:
> We've been running into an issue where the calling BasicReject with
> requeue set to true, puts the message back in front of the line (as a
> stack) instead of the back of the line (as a queue).  This feature
> worked in 2.6.1.  Is there some other setting that needs to be adjusted
> to get this to work the way it should?

The order of messages after requeue is left unspecified by AMQP. You
will find a description of ordering guarantees made by RabbitMQ here:
http://www.rabbitmq.com/semantics.html#ordering

The requeue behaviour changed in v2.7.0. There is no way to obtain the
previous behaviour on recent brokers. The closest approximation to the
previous requeue behaviour is to acknowledge and republish a fresh copy
of the message, which will then be enqueued as a new message.

-Emile