<div dir="ltr">Thanks Matthias, that confirms our suspicions. We'll wait for 3.1.5 and report back if there's still any issues.</div><div class="gmail_extra"><br clear="all"><div>Paul Bowsher</div>
<br><br><div class="gmail_quote">On Thu, Aug 15, 2013 at 11:18 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Paul,<div class="im"><br>
<br>
On 15/08/13 11:14, Paul Bowsher wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Oops sorry, premature send. In the connections view they don't say<br>
blocked, flow or running. When you click the connection it doesn't have<br>
a "state" at all. However rabbitmqctl list_connections lists them as<br>
blocked.<br>
</blockquote>
<br></div>
I suspect you are seeing an effect of <a href="http://rabbitmq.1065348.n5.nabble.com/Many-errors-in-mirrored-queues-with-rabbitmq-3-1-4-tt28801.html" target="_blank">http://rabbitmq.1065348.n5.<u></u>nabble.com/Many-errors-in-<u></u>mirrored-queues-with-rabbitmq-<u></u>3-1-4-tt28801.html</a>. The error message in the logs is certainly due to that.<br>
<br>
So either roll back to 3.1.3 or wait for 3.1.5.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>