<br><br><div class="gmail_quote">On Tue, Nov 10, 2009 at 8:56 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Arun,<br>
<div class="im"><br>
On Tue, Nov 10, 2009 at 08:50:12PM +0530, Arun Suresh wrote:<br>
> > Well, you could simply check to see if the socket is still open. If the<br>
> > broker goes down then your network socket from the client will also go<br>
> > down.<br>
> ><br>
><br>
> :) thing is.. I have clients connected to the RabbitMQ instance that DIDNT<br>
> go down.. but have subscriptions to Queues persisted on the instance that<br>
> did..<br>
> These clients wont know if queue is gone or not...<br>
<br>
</div>Ahh, I see, yes indeed you are right. One way round may be to have<br>
connections open to each node in the cluster, and watch for when those<br>
connections go down. However, that would require that you know which<br>
node each queue is on. Alternatively, your clients could publish with<br>
the mandatory flag set and then you'll get an exception should the<br>
message not be able to be routed to a queue. Unfortunately, no, the kind<br>
of notification you're looking for isn't available in AMQP.<br></blockquote><div>Hmmm... That seems like a decent solution.. thanx </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>