Aug 5th, 2010, 12:25 PM
It seems that Spring's RabbitTemplate does not pay any attention to channel.flow. Even after the RabbitMQ server hits a memory watermark, RabbitTemplate continues to send messages from producers until RabbitMQ dies.
Am I doing something wrong? I think I can get around this by manually checking server status before calling RabbitTemplate.convertAndSend(), but that feels pretty wrong.
More info on channel.flow here http://www.rabbitmq.com/extensions.html#memsup