3 Replies Latest reply: Jun 14, 2012 7:06 PM by John Bullock RSS

    Cascading SlowConsumer Advisories

    John Bullock Newbie

      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.