[rabbitmq-discuss] Hanging connections in management interface (v3.0.4)

Wed May 1 10:06:12 BST 2013

Could this not be due to a TCP half close? 

On Tuesday, 30 April 2013 at 20:35, Maze wrote:

> I think we had a similar problem. Clients that died were still in the 
> list of connections. In our case this was slowing RabbitMQ (v2.6.x ? not 
> sure) down to a degree that we had to restart RabbitMQ.
> We solved the problem by implementing the heartbeat and we haven't seen 
> any such issues since then.
> 
> Cheers
> Maze
> 
> 
> 
> On 2013-04-30 16:04, Simon MacMullen wrote:
> > OK.
> > 
> > So you say "queues show hanging connections". Do you mean that the 
> > management plugin shows connections under the "Connections" tab, or 
> > consumers under queue details, or something else?
> > 
> > Do you see the same items in rabbitmqctl list_connections (or 
> > list_queues or similar)? If so can you send the output of "rabbitmqctl 
> > report"?
> > 
> > Also, do these items ever go away? Has the memory alarm / disk alarm 
> > gone off at any point?
> > 
> > Cheers, Simon
> > 
> > On 30/04/13 14:17, Allan Beaufour wrote:
> > > No, this is a single rabbitmq node.
> > > 
> > > 
> > > On Tue, Apr 30, 2013 at 5:44 AM, Simon MacMullen <simon at rabbitmq.com (mailto:simon at rabbitmq.com)
> > > <mailto:simon at rabbitmq.com>> wrote:
> > > 
> > > 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?
> > > 
> > > Cheers, Simon
> > > 
> > > On 29/04/13 16:23, Allan Beaufour wrote:
> > > 
> > > I've for a long time had an issue where queues show hanging
> > > connections
> > > in the management interface. The queues show a number of 
> > > perpetual
> > > unacked messages and even if I shut down all consumers, these
> > > remain.
> > > The ip+port for the consumers doesn't match any processes 
> > > either. Is
> > > this a known bug?
> > > 
> > > I've had this issues for a while. We were running v2.7.1
> > > perviously and
> > > was secretly hoping they would disappear in the upgrade :)
> > > 
> > > Thanks,
> > > 
> > > Allan
> > > 
> > > 
> > > _________________________________________________
> > > rabbitmq-discuss mailing list
> > > rabbitmq-discuss at lists.__rabbitmq.com (mailto:rabbitmq-discuss at lists.__rabbitmq.com)
> > > <mailto:rabbitmq-discuss at lists.rabbitmq.com>
> > > https://lists.rabbitmq.com/__cgi-bin/mailman/listinfo/__rabbitmq-discuss
> > > <https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
> > > 
> > > 
> > > 
> > > --
> > > Simon MacMullen
> > > RabbitMQ, VMware
> > > 
> > 
> > 
> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com (mailto: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/20130501/7522d892/attachment.htm>