[rabbitmq-discuss] Regarding the blocking state

[Simon MacMullen]

On 25/02/2013 9:54AM, Mattamadugu L N Seshendra wrote:
> Hi,
> I am seshendra, As I was testing the rabbitMQ I have found a problem
> that when my memory (RAM)  reaches its limit, Then I will receive
> a notification and I have noticed that it is blocking the connections.
> So I thing is that what happens to the messages in the blocking state
> whether the messages will be dropped or when rabbitmq comes back to
> normal state then It receives the messages from the point there it is
> blocking.

The producers will (in general, depending on the client library) block - 
i.e. hang - while publishing a message.

So the message hasn't been lost, but neither has RabbitMQ accepted 
responsibility for it.

Once the memory alarm clears then the broker will start accepting 
messages again and the producer should finish publishing - although it's 
not inconceivable that the client could time out (again, depending on 
the client).

So it's not great to be hitting the memory alarm - you should consider 
provisioning more memory (and also upgrading, especially if you are 
running < 2.8 which hit the memory alarm far more often).

Cheers, Simon

> for example
>   Production I was send around 1500messages per second after a
> particular time Rabbit mq comes to blocking state. so production will be
> sending the messages (ex a,b,c,d...) so what happens to these messages
> in the blocking state.
>
> So please explain me and clarify my doubt.
>
> Thanking you in advance
>
>
> With Regards
> Seshendra.
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>