Matthias,<div><br></div><div>Thank you for your response. I will try to investigate more in the application layer in the next few days.</div><div><br></div><div>Regards,</div><div><br clear="all">Maxime Bouroumeau-Fuseau<br>
<br><br><div class="gmail_quote">On Tue, Jul 19, 2011 at 12:30 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Maxime,<div class="im"><br>
<br>
On 19/07/11 10:57, Maxime Bouroumeau-Fuseau wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was using stormed-amqp 0.1 and rabbitmq 2.3.1.<br>
I have updated to the latest master of stormed-amqp and to rabbitmq 2.5.1.<br>
<br>
The problem persists but appears after more messages have been received.<br>
You'll find attached report.txt which is with a consumer without ack and<br>
report_with_ack.txt<br>
</blockquote>
<br></div>
We can see that the 'thot.processor' queue has 863 messages ready, and one consumer, on channel <rabbit@ns353204.3.1624.0>. That channel is associated with connection <rabbit@ns353204.3.1621.0>. That connection has a 'send_pend' count of 8432.<br>
<br>
This indicates that the client is not reading from the rabbit connection socket. So this is either a problem with the client library or with the app. I am not much of a python hacker and am not familiar with stormed-amqp, but I suggest the next step is to figure out what the consumer process is doing when its stuck, i.e. somehow get a stack trace from it.<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br></div>