Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of bruce.snyder@gmail.com
 designates 74.125.44.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=rDKbtpKgoHuBI8WEbe/XMdN8Z9cvWfgzjq1cVpeAdrIyfMFMddX0mH4JbIj5392Cv+
         ViedTM8M2HQP+3/3/LQLcxvqBDfUR6/ugQL/JIZ4fel2J/Fm31MN5ZMJaoesN2oz51Q+
         Md8s2pEtIqNVpPDBDmmNvRKN6eHuhhCbv8n/g=
Message-ID: <7b3355cb0810071508q12f8054do8691dfb06805c921@mail.gmail.com>
Date: Tue, 7 Oct 2008 16:08:23 -0600
From: "Bruce Snyder" <bruce.snyder@gmail.com>
To: users@activemq.apache.org
Subject: Re: Nework of brokers and Topic leak memory
In-Reply-To: <19867244.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <19867244.post@talk.nabble.com>

On Tue, Oct 7, 2008 at 3:04 PM, activemqny <nianlongy@yahoo.com> wrote:
>
> We  use a network of brokers and topic to do messaging. All our message
> producers and consumers talk to the local VM broker. We reply on bridges
> between network of brokers to move messages between brokers.
>
> I attached two files to show this memory leak problem. TryJmsClient keeps
> sending persistent messages to a Topic. TryJmsManager has a message
> consumer. Start TryJmsManager first and then start TryJmsClient. After
> running about 10 seconds, TryJmsClient stops sending because of getting
> "SystemUsage memory limit reached" error. About 24K messages are sent and
> consumer shows it get all messages. Now examine ActiveMQ MemoryUsage
> printout of TryJmsClient, MemoryUsage percentage stays at 100% or 99%
> forever. Producer can never send any more messages.
>
> Note1: If I slow down sending by adding a sleep, I don't see memory leak
> immediately. I am not sure for longer running time.
> Note2: If I use Queue instead of Topic, there is no memory leak.

This is not a memory leak, it's directly related to the way that
producer flow control works:

http://activemq.apache.org/producer-flow-control.html

Try disabling producer flow control in conf/activemq.xml to see if
that takes care of the issue.

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/

Blog: http://bruceblog.org/