Thanks Marek.<div>I am using ack. I solved the problem. Actually i was too ambitious with the performance. Was using threads to queue posting as well. Though not sure exactly why, but there lot of connections and channels were getting created. And these i was not able to relate to any relevant consumer processes. Then i moved these out of thread and did refactoring for passing same connection object. Now there are no more extra (or i'll say orphan) connections and channels. Till now i've not faced problem after the code modification.�</div>
<div><br></div><div>Will rework the same with threads once the current execution gets over.</div><div><br><br><div class="gmail_quote">On Tue, Dec 14, 2010 at 11:30 PM, Marek Majkowski <span dir="ltr"><<a href="mailto:majek04@gmail.com">majek04@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tue, Dec 14, 2010 at 13:24, pradeep w <<a href="mailto:hpk.warrier@gmail.com">hpk.warrier@gmail.com</a>> wrote:<br>
> The situation that i'm running into is like this:<br>
> After processing some entries[random count], suddenly there is no activity<br>
> in RabbitMQ. If i kill one of the consumer, then some activity happens and<br>
> other queues process for some time.Then again it repeats and i kill some<br>
> other consumer. Finally killing all the consumers.<br>
> If i restart all consumers again things work for some time before�showing<br>
> the same inaction behavior.<br>
<br>
</div>Sounds like 'basic.ack' and 'basic.qos' issue.<br>
<br>
Are you using 'basic.qos'?<br>
Are you using acks (no_ack=False) and do you always remember to do basic_ack?<br>
<br>
<a href="http://www.rabbitmq.com/tutorial-two-python.html" target="_blank">http://www.rabbitmq.com/tutorial-two-python.html</a><br>
<br>
Cheers,<br>
<font color="#888888"> �Marek<br>
</font></blockquote></div><br></div>