<div dir="ltr">the second reason is <a href="http://right.it">right.it</a> mybe a bug in kombu/amqp. in kombu it get many message from rabbitmq in SimpleQueue.get method without ack and push the messages into a collections.deque, but sometimes my server has poor network and the client/server disconnected(or mybe a but in amqp lead to the disconnection), then the kombu create a new connection/channel, the messages in noack cannnot be received for a while and then goto ready .this reason makes the messages disorder.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/7 Xie Yunpeng <span dir="ltr"><<a href="mailto:woqimingweipeng@gmail.com" target="_blank">woqimingweipeng@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">thx, i will do some test and analyse log to verify the second condition.i think it is the real reason.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/5/7 Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>On 07/05/2013 09:26, Emile Joubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 06/05/13 11:08, Xie Yunpeng wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I use 4 publisher sending messages to this queue and 1 consumer to<br>
receive the messages.the consumer when connect to the rabbitmq server ,<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i find it receive messages disorder sometimes, just like: first receive<br>
messges in current time and then receive messages several hour ago, the<br>
interval is not regular.<br>
</blockquote>
<br>
<br>
You can find the ordering guarantees here:<br>
<a href="http://www.rabbitmq.com/semantics.html#ordering" target="_blank">http://www.rabbitmq.com/<u></u>semantics.html#ordering</a><br>
In particular, there is no ordering guarantee if you involve multiple<br>
publishers.<br>
</blockquote>
<br></div></div>
Well, there's still exactly the same ordering guarantee as there is with a single publisher: messages from each publishing channel won't get reordered with respect to each other. We just don't guarantee anything about ordering between channels. And indeed it's hard to see how we could.<br>
<br>
To the OP: either something weird is happening in your publishers causing them to buffer messages for hours before sending to RabbitMQ (unlikely I guess but I should mention it) or messages are not being acknowledged by your consumers and are then being requeued once the consumer disconnects. In the latter case all the "late" messages should have the "redelivered" flag set.<br>
<br>
Cheers, Simon<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>