On 30/01/12 13:41, Rob Sutherland wrote: > I'm running rabbitmq-server-2.4.0 Ah, right. That makes much more sense. This was a bug introduced in 2.4.0 and fixed in 2.5.0. I recommend an upgrade. Cheers, Simon -- Simon MacMullen RabbitMQ, VMware