[rabbitmq-discuss] Flow detection in the RabbitMQ Java Client in 3.2.0

[Michael Klishin]

On 24 Oct 2013, at 08:32, Héctor Veiga <kecok0 at gmail.com> wrote:

> 't sending the flag so the FlowListener was not working at all.

Flow control is a deprecated feature. Instead, recent versions of RabbitMQ will block publishers
by not reading from the socket until all alarms (used RAM, # of file available descriptors, disk space available) clear.

Clients are notified about these events as of RabbitMQ 3.2 and only if they indicate that they support
connection.[un]blocked in capabilities.

> Also, there is one new thing called BlockListener at the connection level. I have been trying to find info about this class but the link is broken: http://www.rabbitmq.com/connection_blocked.html .

The correct link is http://www.rabbitmq.com/connection-blocked.html.

What page did you find http://www.rabbitmq.com/connection_blocked.html on?

> Does the BlockListener provide information about when the producer is getting flow or blocked?

Yes, that’s how you register connection.blocked and connection.unblocked listeners in the Java client.

MK