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

Fri Dec 13 17:21:46 GMT 2013

ohh..ok, so just in order to grab the number of messages present, at any
specific instance i can call the queue.declare anytime and pass the passive
parameter.

But considering the cons, the amqp_consume_message sounds better. But this,
is a good thing we can try and see for an experimental purpose.

We are using 2.8.7 rabbitmq which does not seem, to have the
amqp_consume_message, seems like it's a recent addition to your library.
Seems like it's time for us to upgrade :-)

Kind Regards
Raj

On Fri, Dec 13, 2013 at 10:36 PM, Alan Antonuk [via RabbitMQ] <
ml-node+s1065348n32081h99 at n5.nabble.com> wrote:

> 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 <[hidden email]<http://user/SendEmail.jtp?type=node&node=32081&i=0>
> > 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
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=32081&i=1>
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=32081&i=2>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://rabbitmq.1065348.n5.nabble.com/Why-is-the-select-always-getting-timed-out-in-consumer-tp32046p32081.html
>  To unsubscribe from Why is the "select" always getting timed out in
> consumer?, click here<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=32046&code=cmFqLmt1bWFyLnNhbnB1aUBnbWFpbC5jb218MzIwNDZ8MTUwNTg3MDEzOA==>
> .
> NAML<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Why-is-the-select-always-getting-timed-out-in-consumer-tp32046p32082.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131213/cb0dd4bf/attachment.html>