<p>Hi Luke, more or less. This behavior is influenced by the prefetch-count setting, which dictates how many messages are delivered to a consumer in advance before they are acked. If you set it to 1, then you will achieve what you describe.</p>
<div class="gmail_quote">On Mar 4, 2012 9:17 PM, "luke manner" <<a href="mailto:lukemanner@gmail.com">lukemanner@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span>Hi,</span><div>I'm defining a Camel RabbitMQ component.</div><div>In route definition it is possible to define the number of concurrent consumers on a specific endpoint.</div><div>If we suppose that user want to use a queue (in JMS style),</div>
<div>I have to declare just only the queue (default exchange is used).</div><div><br></div><div><br></div><div>On this queue multiple consumers can asynchronously obtain a message and this message is delivered through camel to receivers.</div>
<div>Do you have any hint on how manage multiple consumers? All of them have to use the basicConsume and the broker ensures that different messages are provided to consumers in a round robin way?</div><div><br>
</div><div>Any help will be appreciate.</div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div>