[rabbitmq-discuss] Why does the queue drop other messages after the first is consumed?
Raj Kumar Sanpui
raj.kumar.sanpui at gmail.com
Mon Dec 16 17:42:16 GMT 2013
The logs doesn't seem to be of much info, the "abrupt close" is because i
pressed Ctrl + C.
Here is the log:
=INFO REPORT==== 16-Dec-2013::10:05:59 ===
accepting AMQP connection <0.32684.1> ([::1]:59097 -> [::1]:5672)
=INFO REPORT==== 16-Dec-2013::10:05:59 ===
accepting AMQP connection <0.32693.1> ([::1]:59098 -> [::1]:5672)
=INFO REPORT==== 16-Dec-2013::10:06:00 ===
accepting AMQP connection <0.32701.1> ([::1]:59099 -> [::1]:5672)
=INFO REPORT==== 16-Dec-2013::10:06:00 ===
accepting AMQP connection <0.32705.1> ([::1]:59100 -> [::1]:5672)
=INFO REPORT==== 16-Dec-2013::10:06:00 ===
accepting AMQP connection <0.32717.1> ([::1]:59101 -> [::1]:5672)
=INFO REPORT==== 16-Dec-2013::10:06:00 ===
accepting AMQP connection <0.32721.1> ([::1]:59102 -> [::1]:5672)
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32684.1> ([::1]:59097 -> [::1]:5672):
connection_closed_abruptly
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32701.1> ([::1]:59099 -> [::1]:5672):
connection_closed_abruptly
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32693.1> ([::1]:59098 -> [::1]:5672):
connection_closed_abruptly
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32705.1> ([::1]:59100 -> [::1]:5672):
connection_closed_abruptly
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32717.1> ([::1]:59101 -> [::1]:5672):
connection_closed_abruptly
=WARNING REPORT==== 16-Dec-2013::10:06:01 ===
closing AMQP connection <0.32721.1> ([::1]:59102 -> [::1]:5672):
connection_closed_abruptly
On Mon, Dec 16, 2013 at 11:07 PM, Michael Klishin <
michael.s.klishin at gmail.com> wrote:
>
> 2013/12/16 Raj Kumar Sanpui <raj.kumar.sanpui at gmail.com>
>
>> After i call:
>> amqp_basic_consume(conn, 1, queuename, amqp_empty_bytes, 0, 1, 0,
>> amqp_empty_table);
>>
>> Right after this call, the messages are truncated to 0.
>>
>
> As soon as there is a consumer on this queue, RabbitMQ will deliver
> messages to it
> as fast as possible, because you use automatic acknowledgements. Use
> manual acks
> and basic.qos if that's not what you want.
>
> Local debug statements are of limited use in this case. What you need is
> to trace what's going
> down the wire.
>
> What's in RabbitMQ log? It's very important to understand if there are
> any channel exceptions.
> --
> MK
>
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131216/2bc6ffc5/attachment.html>
More information about the rabbitmq-discuss
mailing list