Hi Mathew..<br><br><div class="gmail_quote">On Tue, Nov 10, 2009 at 8:46 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 Mon, Nov 09, 2009 at 07:58:36AM +0530, Arun Suresh wrote:<br>
> > Can you elaborate on this issue a bit? Is this redirection coming back<br>
> > from the server?<br>
> ><br>
> Yes.. I guess its a redirection request coming from the server..<br>
> basicaly.. the response to my 'connection.open' request is a<br>
> 'conncetion.redirect' which on recipt, the client throws an exception and<br>
> exits..<br>
> ive gotten around this issue by setting 'insist = true' in the request<br>
> record...<br>
> Maybe ill look at the Java client and see whats done there ?<br>
<br>
</div>The redirection stuff has gone from AMQP 0.9.1 so there's not a huge<br>
need to worry about it if you're just experimenting for the time being.<br>
The idea is that in a cluster, a node can request that you change the<br>
connection to a different node, for load balancing reasons. The Java and<br>
.Net clients both detect these errors and attempt to obey the<br>
redirection requests.<br>
<div class="im"><br>
> > Well client@m1 died. This means its subscriptions to Q were lost - there<br>
> > is no concept of persisting subscriptions, so when rabbit@m1 comes back<br>
> > up, the Q will have no consumers at all. If you restart client@m2 then<br>
> > yes, it'll recreate its subscription to Q, and thus receive all the msgs<br>
> > sent to that Q. If you also restart client@m1 then that too will<br>
> > recreate its subscription to Q and share the msgs with client@m2 as<br>
> > before.<br>
> ><br>
><br>
> Confirms what ive been thinking... But Is there any way for clients to be<br>
> notified of dead subscriptions ? That would be helpful, else i would have to<br>
> keep polling something to get that information..<br>
<br>
</div>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></blockquote><div><br></div><div>:) thing is.. I have clients connected to the RabbitMQ instance that DIDNT go down.. but have subscriptions to Queues persisted on the instance that did..</div><div>These clients wont know if queue is gone or not... </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Matthew<br>
</font></blockquote></div>-Arun