Return-Path: 
 <dev-return-20505-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 81069 invoked from network); 2 Jun 2010 14:46:17 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 2 Jun 2010 14:46:17 -0000
Received: (qmail 35587 invoked by uid 500); 2 Jun 2010 14:46:17 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 35561 invoked by uid 500); 2 Jun 2010 14:46:17 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 35552 invoked by uid 99); 2 Jun 2010 14:46:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 14:46:17 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 14:46:14 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o52EjqU6009452
	for <dev@activemq.apache.org>; Wed, 2 Jun 2010 14:45:53 GMT
Message-ID: <23744044.7701275489952609.JavaMail.jira@thor>
Date: Wed, 2 Jun 2010 10:45:52 -0400 (EDT)
From: "Nathan Bryant (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2533) OutOfMemory provoked by Advisory
 messages
In-Reply-To: <1295178577.1260816172847.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/activemq/browse/AMQ-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bryant updated AMQ-2533:
-------------------------------

    Attachment: SlowConsumerTest.java

regression test

> OutOfMemory provoked by Advisory messages
> -----------------------------------------
>
>                 Key: AMQ-2533
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2533
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0, 5.3.0
>            Reporter: Philippe Mouawad
>            Assignee: Rob Davies
>            Priority: Critical
>             Fix For: 5.3.1, 5.4.0
>
>         Attachments: activemq-OOM-ADVISORY.xml, activemq-Workaround-OOM-ADVISORY.xml, activemq.xml, Image 11.png, SlowConsumerTest.java, ThreadDump.txt, TopicListener.java, TopicPublisher.java
>
>
> Hello,
> We are in an environment where we have 1 Broker and 6 clients listener to one Topic.
> We enabled advisory messages through:
> <policyEntry topic=">" memoryLimit="5mb" producerFlowControl="true"  advisoryWhenFull="true" advisoryForSlowConsumers="true"
>                       sendAdvisoryIfNoConsumers="true">
> And sendFailIfNoSpace:
> <systemUsage>
>             <systemUsage sendFailIfNoSpace="true">
>                 <memoryUsage>
>                     <memoryUsage limit="50 mb"/>
>                 </memoryUsage>
>                 <storeUsage>
>                     <storeUsage limit="1 gb" name="foo" store="#store"/>
>                 </storeUsage>
>                 <tempUsage>
>                     <tempUsage limit="100 mb"/>
>                 </tempUsage>
>             </systemUsage>
>         </systemUsage>
> We also have a monitoring process that listens to advisory messages related to the concerned TOPIC.
> After some run, we end up with OutOfMemory.
> OutOfMemory analysis shows:
> - 3372 instances of org.apache.activemq.command.ActiveMQTopic occupying 23,7%
> Names of Topic contain ActiveMQ.Advisory.FULL.Topic:
> - ActiveMQ.Advisory.FULL.Topic.ActiveMQ.Advisory.FULL.Topic.ActiveMQ.Advisory.FULL.....ActiveMQ.Advisory.Producer.Topic.OFBTopic
> 1069 instances of org.apache.activemq.thread.DedicatedTaskRunner$1 holding 12% through the names of the thread that are soooooo long.
> Debuging ActiveMQ, I noticed that AMQ didn't check when sending advisory messages that advisory concerns an advisory.
> Example, suppose you set a listener for advisory message ActiveMQ.Advisory.FULL.Topic.OFBTopic and this listener becomes slow for a reason, then AMQ will send an advisory on this advisory provoking more and more traffic 
> on the broker only for this advisory.
> I attached a Stack Trace showing that an advisory will be sent for the advisory.
> I will be checking to see if this issue also exists on 5.3.0.
> Thanks in advance.
> Philippe.
> http://www.ubik-ingenierie.com

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.