[rabbitmq-discuss] Per Connection Flow Control Issue

[Brendan Hay]

I have a strange occurrence with ruby-amqp 0.9.8 and RabbitMQ 2.8.7 /
Erlang R15B02:

Out of a few hundred connections, it appears that less than half a dozen
are marked as 'flow' in the mgmt interface.
The actual channels belonging to these connections are _not_ marked as
blocked, and are considered 'idle'.

On the client machines, netstat shows the peer sockets to have huge (and
growing) send queues.

Does anybody have any experience with similar problems? I am yet to catch
it in the act,
but it appears flow control must kick in at some point and the connection
simply does not
resume reading the pending bytes off the socket after it is issued new
credits.

Posted this here as I'm not sure who/what to point the proverbial finger
at, suggestions appreciated.

- Brendan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121025/dca27542/attachment.htm>