Yes, so what should the expected observation be - the client code carries on publishing into a black hole,<div>which means the send queue on the client/peer socket should keep growing, and when the rabbit reader is</div><div>
issued new credits, it will lap it all up?</div><div><br></div><div>It just seems the 'flow' status in the UI stays on permanently, it doesn't seem to be toggling at high speed, just locked.</div><div><br></div>
<div>Currently trying to create a small harness to reproduce this locally.</div><div><br></div><div>Thanks,</div><div>Brendan</div><div><br></div><div><div><div><br><div class="gmail_quote">On Thu, Oct 25, 2012 at 4:52 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 25/10/12 15:27, Michael Klishin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Because amqp gem does not do any implicit or automatic flow control, I'd<br>
expect the root cause<br>
to be in EventMachine. Do you have a way to reproduce this issue?<br>
</blockquote>
<br></div>
The flow control at the server side is implemented by just not reading from the socket. So clients do not need to do anything; publishing will just block.<div><br>
<br>
Cheers, Simon<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br></div><div><div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>
</div></div>