[rabbitmq-discuss] Weird Issue when cluster member restarts

[Arun Suresh]

On Tue, Nov 10, 2009 at 8:56 PM, Matthew Sackman <matthew at lshift.net> wrote:

> Hi Arun,
>
> On Tue, Nov 10, 2009 at 08:50:12PM +0530, Arun Suresh wrote:
> > > Well, you could simply check to see if the socket is still open. If the
> > > broker goes down then your network socket from the client will also go
> > > down.
> > >
> >
> > :) 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..
> > These clients wont know if queue is gone or not...
>
> Ahh, I see, yes indeed you are right. One way round may be to have
> connections open to each node in the cluster, and watch for when those
> connections go down. However, that would require that you know which
> node each queue is on. Alternatively, your clients could publish with
> the mandatory flag set and then you'll get an exception should the
> message not be able to be routed to a queue. Unfortunately, no, the kind
> of notification you're looking for isn't available in AMQP.
>
Hmmm... That seems like a decent solution.. thanx

>
> Matthew
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091110/376cd7c2/attachment.htm