Hi, it looks like indeed you have a slow consumer on "slow consumer" advisory topic. Can you raise a jira for this?
Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. dej...@fusesource.com | fusesource.com skype: dejan.bosanac | twitter: @dejanb blog: http://www.nighttale.net ActiveMQ in Action: http://www.manning.com/snyder/ On Fri, Jun 15, 2012 at 12:13 AM, jbull...@iqnavigator.com <jbull...@iqnavigator.com> wrote: > I recently experienced an activemq failure where the service became > unresponsive. A thread dump showed a large number of threads whose names > indicated they were related to ActiveMQ.Advisory.SlowConsumer.Topic.xxx But > the weird thing is that the topic that was being alerted on was another slow > consumer advisory topic! This was repeated over and over with deeper and > deeper nesting. An example: > > "Topic > ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Advisory.SlowConsumer.Topic.ActiveMQ.Adviso > ..... > > This is an indication to me that ActiveMQ is recursively creating > SlowConsumer advisory topics on it own advisory topics. > > My only solution was to restart the process. > > Does anyone have any idea what was going on? This has happened occasionally > before and I would really like to know what is happening. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Cascading-SlowConsumer-Advisories-tp4653301.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
