<p>Hi Lowell,</p>
<p>The second tutorial does not use a topic exchange, but even with a topic exchange the situation would be the same. The key point here is that your workers are reading messages from the same queue. The exchange, topic or anything else, as soon as it has delivered a message to a queue is out of the game. The queue receives the message because it's bound to the exchange. Then you have two or more workers reading from the same queue, thereby receiving each one message in a round-robin fashion.</p>
<div class="gmail_quote">On Jun 30, 2011 11:29 PM, <<a href="mailto:Lowell.Boggs@emc.com" target="_blank">Lowell.Boggs@emc.com</a>> wrote:<br type="attribution">> I am confused by my experiments with rabbitmq-c.<br>
> <br>> I was trying to follow the task worker tutorial:<br>
> <br>> <a href="http://www.rabbitmq.com/tutorials/tutorial-two-python.html" target="_blank">http://www.rabbitmq.com/tutorials/tutorial-two-python.html</a><br>> <br>> Of course, I'm using C interfaces not the python or Java interfaces.<br>
> <br>> Being a newbie it is probable that I'm doing something wrong, but:<br>> <br>> The tutorial implies to me that if I have:<br>> <br>> * one exchange+topic<br>> * two worker executables that read from it<br>
> <br>> then<br>> <br>> * due to round-robin processing, some messages will go to one executable<br>> * other messages will go to the other<br>> <br>> However, I am seeing that both exectuables receive all the messages -- which is not at all what I want.<br>
> <br>> Is this supposed to work with the default version of rabbitmq-c?<br>> <br>> Immediately upon logging into the channel, in the consumers, I am setting<br>> <br>> basic_qos(conn, 1, 0, 1, 0);<br>
> <br>> Also, I am calling basic_consume like this:<br>> <br>> amqp_basic_consume(conn,<br>> 1,<br>> amqp_cstring_bytes(queuename),<br>> amqp_empty_bytes,<br>
> 0,<br>> 0,<br>> 0,<br>> amqp_empty_table<br>> );<br>> <br>> <br>> The exchange that i am using is amq.direct. I have tried an empty string queue name as well as "hello".<br>
> <br>> I am calling basic_ack() as soon as I receive the messages in both worker executables -- well, after I log their reception.<br>> <br>> Any ideas?<br>> <br>> Thanks,<br>> Lowell<br>> <br>
> <br>
> <br>> <br></div>