[rabbitmq-discuss] Producers hanging when reaching high memory watermark on 1.8.1

Dave Greggory davegreggory at yahoo.com
Fri Aug 13 18:04:33 BST 2010

In one of our load tests, we found that RabbitMQ causes producers to hang when it reaches the high memory watermark. We expected RabbitMQ to hang and but not the producers. How can we work around it?

Is there a way to configure RabbitMQ to close the connection or throw an exception from the client API when that happens so the producers can respond. Or maybe there's a timeout I can specify for sends? If there's no timeout can that thread be interrupted when it hangs?

It's imperative that our client apps remain unaffected if RabbitMQ blows up in any way. 

We're connecting to RabbitMQ 1.8.1 nodes using 1.8.1 java client running under Spring-AMQP 1.0M1. 

More information about the rabbitmq-discuss mailing list