[rabbitmq-discuss] [rabbitmq-erlang-client] Missing 1 queue message after nodedown message from another node.
virolord at gmail.com
Fri Mar 9 18:58:41 GMT 2012
I have a small OTP App ( say node A), that subscribes to a RabbitMQ queue,
and also talks to another erlang node in another process ( node B ).
Now, sometimes the process hosting node B crashes for some reason, and my
node A gets a 'nodedown' message. Up till this point, consumption from
RabbitMQ works perfectly.
However, after my handle_info has finished processing the nodedown, if I
publish a message to the RabbitMQ queue, my app doesn't consume it.
However, all messages published after this one are consumed properly and
processed. However that 1 message remains in a message_unacknowledged state
in the queue, even though my handle_info refuses to have ever consumed it !
Is this a known issue in the client ? Can someone please help me ?
Rabbitmq server version : 2.7.1
Rabbitmq client version : 0.9.1 version of the AMQP protocol
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss