[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 18:48:54 GMT 2013
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>
> > 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
> Software Engineer, Pivotal/RabbitMQ
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss