Hi Robert,<br><br>If you set the QOS on the consumer to 1 (as you say), then this should prevent the message being queued at the client.<br><br>Thanks,<br>Paul.<br><br><div class="gmail_quote">On Wed, Oct 7, 2009 at 12:28 PM, Robert Raschke <span dir="ltr"><<a href="mailto:rtrlists@googlemail.com">rtrlists@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I'm wondering if I'm wandering the right path here. (I'm using 1.6.0 with erlang client.)<br>
<br>I was intending to use a basic.publish with mandatory and immediate set to true, and a return handler to allow me to add new workers reading from a queue.<br>
<br>I create a work queue with a return handler and a reply queue. I also create one initial worker, subscribing to the work queue with no_ack set to false.<br><br>I then publish a work message onto the work queue and the worker picks it up, does the work and publishes the answer back into the reply queue.<br>
<br>My intention was that my work message publish uses the immediate flag to generate a basic.return if the message cannot be immediately delivered. I thought that if my worker is busy it won't get the next message, leading to the basic.return. But I believe my thinking is wrong. It looks like the second work message is routed to the initial work consumer immediately, even if it is still busy.<br>
<br>Have I overlooked something obvious, or would I need to implement a 1 message flow control on the channel that the work consumer is using?<br><br>Thanks for any pointers,<br>Robby<br><br>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>