Thanks, I got it.<br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 9:04 AM, Tim Watson <span dir="ltr"><<a href="mailto:tim@rabbitmq.com" target="_blank">tim@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 07/09/2012 01:45 PM, Prashanth M wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Tim,<br>
<br>
Yes, I am trying to see what happens if you've got two nodes and one goes down. Clustering doc describes about the cluster setup, it does not tell how to test the cluster<br>
I have two nodes, when I bring down a node with rabbitmqctl stop_app, my web app stops working. I am not sure what I am doing wrong. But I can see that the queues are duplicated between two nodes. my web app pointing to the stomp on the node that is brought down.<br>
<br>
</blockquote>
<br></div>
Maybe you should connect your web app to the node you're *not* bringing down? Reliable though Rabbit is, clustering does not magically relocate client connections when nodes go down.<br>
<br>
HTH!<span class="HOEnZb"><font color="#888888"><br>
<br>
Tim<br>
</font></span></blockquote></div><br>