<br><div class="gmail_quote">On Fri, Mar 9, 2012 at 6:58 PM, Abhinav Jha <span dir="ltr"><<a href="mailto:virolord@gmail.com">virolord@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, <div><br></div><div>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 ).</div><div><br></div><div>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. </div>
<div><br></div><div>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 !</div>
<div><br></div><div>Is this a known issue in the client ? Can someone please help me ? </div><div><br></div><div>Rabbitmq server version : 2.7.1</div><div>Rabbitmq client version : 0.9.1 version of the AMQP protocol</div>
<div>Erlang: R15B </div><div><br></div><div>Thanks !</div>
<br></blockquote></div><br>I would say a lot depends on what your "node A" code is doing in the
handling of the nodedown info message. Are you using any State in your
gen_server? If yes, could that be impacting your RabbitMQ message handling in
any way? For example, leading to not ack'ing a msg?<br>
<br>
Robby<br><br>