[rabbitmq-discuss] rabbitmq query

Mon Sep 12 09:45:41 BST 2011

>Examples where the condition of a single path does not hold is when a
>consumer reconnects or requeues messages. In these cases you cannot rely
>on messages being received in publication order.

When u say reconnects or requeues. I assume that the application using queue to receive message crashes and then it connects
again to receive the message at that moment u cannot gaurantee the order right

Please confirm.

Regards,

Nithesh

From: Emile Joubert <emile at rabbitmq.com>
To: Nithesh Shetty <knitheshshetty at yahoo.com>
Cc: "rabbitmq-discuss at lists.rabbitmq.com" <rabbitmq-discuss at lists.rabbitmq.com>
Sent: Monday, September 12, 2011 1:35 PM
Subject: Re: [rabbitmq-discuss] rabbitmq query

Hi Nithesh,

Op 12/09/11 06:35, het Nithesh Shetty geskryf:
> Hi,
>  
> I have read blog saying the order of the message in rabbitmq is not
> maintenained i.e it the order of the message sent can alter when receive.

RabbitMQ maintains the order of messages as required by the
specification. See section 4.7 for the AMQP 0-9-1 spec:

---
contents flowing through a single path within the server will remain
ordered. For contents of a given priority flowing through a single path,
we define a content processing path as consisting of one incoming
channel, one exchange, one queue, and one outgoing channel.
---

Examples where the condition of a single path does not hold is when a
consumer reconnects or requeues messages. In these cases you cannot rely
on messages being received in publication order.

However we are currently implementing an enhancement that will allow
ordering to be maintained in the case where a single consumer consumes
from a queue. This has not been released yet.

-Emile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110912/dfb20e57/attachment.htm>