[rabbitmq-discuss] Orphaned channels after connection close in Rabbit 3.1.4

[Paul Bowsher]

Thanks Matthias, that confirms our suspicions. We'll wait for 3.1.5 and
report back if there's still any issues.

Paul Bowsher


On Thu, Aug 15, 2013 at 11:18 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Paul,
>
>
> On 15/08/13 11:14, Paul Bowsher wrote:
>
>> Oops sorry, premature send. In the connections view they don't say
>> blocked, flow or running. When you click the connection it doesn't have
>> a "state" at all. However rabbitmqctl list_connections lists them as
>> blocked.
>>
>
> I suspect you are seeing an effect of http://rabbitmq.1065348.n5.**
> nabble.com/Many-errors-in-**mirrored-queues-with-rabbitmq-**
> 3-1-4-tt28801.html<http://rabbitmq.1065348.n5.nabble.com/Many-errors-in-mirrored-queues-with-rabbitmq-3-1-4-tt28801.html>.
> The error message in the logs is certainly due to that.
>
> So either roll back to 3.1.3 or wait for 3.1.5.
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130815/6c59065d/attachment.htm>