[rabbitmq-discuss] Can't Bind After Upgrading from 3.1.1 to 3.1.5

[Chris]

Hi Michael,

I don't think it is easily reproducible.  We haven't run into this with any
of our upgrade tests or at other customer sites.  So... I wouldn't know how
to create a script that reproduces the problem.

If it is helpful to have the actual queue, routing key, and exchange names,
then here you go (they actually aren't that special-- not sure why I
censored them the first time):
Queue: mail.global.v0.requests
RoutingKey: mail.global.v0.requests
Exchange: Local.Requests

This happened with two queues.  There are about 10 other durable queues
with similar names/keys (and the same exchange) that do not have this
problem.

-Chris

-Chris


On Fri, Sep 20, 2013 at 1:23 PM, Michael Klishin <
michael.s.klishin at gmail.com> wrote:

>
> 2013/9/20 Chris <stuff at moesel.net>
>
>> Is there anything I can or should do on my end to further debug /
>> investigate?
>
>
> Can you post actual routing keys you use (both that do not work and do
> work)
> and create a script that can reproduce your issue?
> --
> MK
>
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://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/20130920/0449d91f/attachment.htm>