[rabbitmq-discuss] Windows RabbitMQ Crashes and Blue Screens under Load

Simon MacMullen simon at rabbitmq.com
Fri Jan 13 11:49:47 GMT 2012

On 12/01/12 17:55, james.poole at rsa.com wrote:
> Everything hums along until the vm_memory_high_watermark is triggered
> and then we see the crash.  One interesting thing is that in the log it
> still shows it accepting and starting tcp connections after the memory
> alarm is triggered (for around 15 seconds before the crash).  I thought
> this was supposed to block until the memory was under control?

It won't refuse connections. The idea is that it should accept 
connections, but then block them if they try to publish. If you want to 
connect to consume messages you should be allowed to even after the 
alarm is triggered...

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list