[rabbitmq-discuss] Pathological dead queue behavior in a cluster.

[Jason J. W. Williams]

On Wed, Mar 30, 2011 at 3:58 PM, Jason J. W. Williams <
jasonjwwilliams at gmail.com> wrote:

> Very interesting. I assume the exchange in a fanout exchange (I see no
>> routing key in your list_bindings output). When in this "broken" state,
>> what happens if you publish to the queue with mandatory set?
>
>
> The exchange is a direct exchange. With mandatory set it doesn't raise any
> exceptions.
>
> I'm noticing the output of list_bindings is different after the node
> restart and then after the redeclare.
>
> Before Restart:
>
> Listing bindings ...
> exchange cluster_test queue cluster_test []
> cluster_test exchange cluster_test queue cluster_test []
> ...done.
>
> While Node Is Down:
> Listing bindings ...
> ...done.
>
> After Restart:
>
> Listing bindings ...
>  exchange cluster_test queue cluster_test []
> ...done.
>
>
> It looks like there's an extra binding that doesn't get recreated.
>
> -J
>

Of related note at Alvaro's suggestion I tried publishing into the ""
exchange with the queue as the routing key when the binding is
non-functional. That puts the message into the queue as expected.

-J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110330/ebe0895a/attachment.htm>