[rabbitmq-discuss] Per Connection Flow Control Issue

Brendan Hay brendan at soundcloud.com
Fri Oct 26 11:23:12 BST 2012

Yes, so what should the expected observation be - the client code carries
on publishing into a black hole,
which means the send queue on the client/peer socket should keep growing,
and when the rabbit reader is
issued new credits, it will lap it all up?

It just seems the 'flow' status in the UI stays on permanently, it doesn't
seem to be toggling at high speed, just locked.

Currently trying to create a small harness to reproduce this locally.


On Thu, Oct 25, 2012 at 4:52 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 25/10/12 15:27, Michael Klishin wrote:
>> Because amqp gem does not do any implicit or automatic flow control, I'd
>> expect the root cause
>> to be in EventMachine. Do you have a way to reproduce this issue?
> 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.
> Cheers, Simon
> --
> Simon MacMullen
> RabbitMQ, VMware
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121026/404112b8/attachment.htm>

More information about the rabbitmq-discuss mailing list