[rabbitmq-discuss] Why does the queue drop other messages after the first is consumed?

[Raj Kumar Sanpui]

Seems like rabbitmq has an allergy towards thread locks.
Invoke a consumer thread (basic.consume) calling pthread_mutex_lock( ) and
all but one message gets dropped. Same works absolutely fine, if no thread
locks are used.


On Mon, Dec 16, 2013 at 11:22 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 16 Dec 2013, at 21:47, Raj Kumar Sanpui <raj.kumar.sanpui at gmail.com>
> wrote:
>
> > In between, do we have any man page for basic.consume?
> >
> > What does "no ack", "exclusive", "local" stands for?
>
> Ignore local. Exclusive means that there can only ever be one consumer on
> the queue.
>
> no ack means “no manual ack”, that is, you don’t intend to use manual
> acknowledgements of
> deliveries. See tutorial 2: http://www.rabbitmq.com/getstarted.html
> and http://www.rabbitmq.com/amqp-0-9-1-reference.html#domain.no-ack
>
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
>
> _______________________________________________
> 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/20131217/490b6ded/attachment.html>