[rabbitmq-discuss] Why is the "select" always getting timed out in consumer?
raj.kumar.sanpui at gmail.com
Fri Dec 13 16:56:43 GMT 2013
Thanks a lot Alan.
I will use that. It really helps.
On Fri, Dec 13, 2013 at 10:24 PM, Alan Antonuk [via RabbitMQ] <
ml-node+s1065348n32079h37 at n5.nabble.com> wrote:
> Don't use select(2). Use one of the higher-level APIs I suggested earlier.
> On Fri, Dec 13, 2013 at 8:46 AM, kingsmasher1 <[hidden email]<http://user/SendEmail.jtp?type=node&node=32079&i=0>
> > wrote:
>> Hi Alan,
>> For the purpose of the POC, we are creating the queue ourselves and
>> publishing the messages, but in the real application, the queue will be
>> already present and created by a backend (Java), and we have to just go
>> ahead and consume in the frontend (which is in C/C++) based on the
>> availability of messages in queue, and spawn a thread for consuming each
>> messages of queue for fast processing.
>> In betwn. before trying the other consume method (with timeout you
>> suggested) i thght to give it a last go and i just bind my queue, right
>> after creation, and i can see the messages getting persisted, i removed
>> O_NOBLOCK option too, but still it gets timedout.
>> Any hint.
>> View this message in context:
>> Sent from the RabbitMQ mailing list archive at Nabble.com.
>> rabbitmq-discuss mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=32079&i=1>
> rabbitmq-discuss mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=32079&i=2>
> If you reply to this email, your message will be added to the discussion
> 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==>
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Why-is-the-select-always-getting-timed-out-in-consumer-tp32046p32080.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss