[rabbitmq-discuss] Why is the "select" always getting timed out in consumer?

Alan Antonuk alan.antonuk at gmail.com
Fri Dec 13 17:04:40 GMT 2013

Assuming you pass in the same parameters; calling declare.queue on a queue
a second time will not have any effect.  If you don't want to create the
queue on the broker if it doesn't exist - you can use the 'passive' flag,
which will prevent the queue from being created in the event the queue
doesn't already exist on the broker.

On Fri, Dec 13, 2013 at 8:53 AM, kingsmasher1 <raj.kumar.sanpui at gmail.com>wrote:

> Sorry, for being unclear, the purpose of writing my first paragraph was, we
> can't use queue.declare, since in the real app, the queue will already be
> declared.
> Thanks
> Raj
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/Why-is-the-select-always-getting-timed-out-in-consumer-tp32046p32078.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> 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/20131213/a16e6461/attachment.html>

More information about the rabbitmq-discuss mailing list