<div class="gmail_extra">2012/11/26 Rajesh <span dir="ltr"><<a href="mailto:rajesh@saksestechnologies.com" target="_blank">rajesh@saksestechnologies.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Based on what I have seen in the samples we will have to run as many instances of worker.java as the number of consumers we
</div>
<div>
would need. Is this correct? If so what are the best practices in doing the same in java (from a deployment perspective)?
</div>
<div>
</div>
<div>
I am also thinking having one worker.java spawning multiple threads and each thread would register with the queue as a different
</div>
<div>
consumer. Is this possible? If so any pitfalls we need to be aware of?</div></blockquote></div><br>Using multiple threads is a better idea. I'd recommend using a separate channel for each thread, primarily because</div>
<div class="gmail_extra">error handling works on per-channel basis with RabbitMQ.<br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
<br>
</div>