<div dir="ltr">No, this is a single rabbitmq node.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 30, 2013 at 5:44 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There is a known issue with connections / channels on a cluster node not being cleared out of mgmt if they were running when the node shuts down. That's not fixed in 3.0.4 but is fixed in nightlies / will be in 3.1.0. Does that sound like what you're seeing?<br>
<br>
Cheers, Simon<br>
<br>
On 29/04/13 16:23, Allan Beaufour wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've for a long time had an issue where queues show hanging connections<br>
in the management interface. The queues show a number of perpetual<br>
unacked messages and even if I shut down all consumers, these remain.<br>
The ip+port for the consumers doesn't match any processes either. Is<br>
this a known bug?<br>
<br>
I've had this issues for a while. We were running v2.7.1 perviously and<br>
was secretly hoping they would disappear in the upgrade :)<br>
<br>
Thanks,<br>
<br>
Allan<br>
<br>
<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
<br><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>