[rabbitmq-discuss] Testing lightweight publisher confirms

Simon MacMullen simon at rabbitmq.com
Thu Dec 1 14:42:39 GMT 2011

On 01/12/11 14:29, Simon MacMullen wrote:
> On 01/12/11 14:25, Adam Rabung wrote:
>> Secondly, what are the most common causes of
>> ConfirmListener.handleNack being called, since server connectivity
>> problems seem to immediately kill the channel?
> An individual queue process crashing within RabbitMQ. That's the only
> thing that can do it. Obviously this makes it rather difficult to test.

Ah, hang on. One way to "crash" a queue is to have it running on a 
single node in a cluster and take that node down. So:

1) Create a two node cluster, node1 and node2.
2) Create a non-mirrored queue on node1.
3) Start a publisher using confirms on node2, publishing to that queue.
4) Stop node1.

You should see nacks then I think.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list