[rabbitmq-discuss] Pika and Channel.Flow

allan bailey zirpubolci at gmail.com
Mon May 24 21:48:31 BST 2010


On Mon, May 24, 2010 at 12:54 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Allan,
> allan bailey wrote:
>> Apparently the AMQP protocol does not
>> send an exception to an active client connection until it reconnects or
>> re-requests access.
> When the memory alarm is raised, RabbitMQ sends a channel.flow on all
> channels. There are no delays other than the usual processing and networking
> delays.
> Also, access.request is a no-op in RabbitMQ and has been removed from the
> AMQP spec in 0-9-1. There is on need for clients to ever invoke it.
So should I just redeclare my exchange, would that be a sufficient no-op?

 I tested it just now and it works to trigger the alert.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100524/c3f3fac6/attachment.htm 

More information about the rabbitmq-discuss mailing list