Return-Path: 
 <dev-return-12203-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 55020 invoked from network); 4 Sep 2008 16:10:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Sep 2008 16:10:13 -0000
Received: (qmail 79998 invoked by uid 500); 4 Sep 2008 16:10:11 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 79972 invoked by uid 500); 4 Sep 2008 16:10:11 -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 79961 invoked by uid 99); 4 Sep 2008 16:10:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2008 09:10:11 -0700
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.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2008 16:09:21 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id A3AC7234C1CB
	for <dev@activemq.apache.org>; Thu,  4 Sep 2008 09:09:52 -0700 (PDT)
Message-ID: <490589997.1220544592668.JavaMail.jira@brutus>
Date: Thu, 4 Sep 2008 09:09:52 -0700 (PDT)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-1833) Topic messages cause MemoryUsage to
 increase slowly over time
In-Reply-To: <1098762382.1214865600266.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

Rob Davies updated AMQ-1833:
----------------------------

    Fix Version/s: 5.2.0
                       (was: 5.3.0)

> Topic messages cause MemoryUsage to increase slowly over time
> -------------------------------------------------------------
>
>                 Key: AMQ-1833
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1833
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Trevor Pounds
>            Assignee: Rob Davies
>            Priority: Critical
>             Fix For: 5.2.0
>
>         Attachments: r672943.diff
>
>
> In our particular scenario we were using ActiveMQ 5.0.0.14-fuse with ServiceMix 3.2.1 and JMS binding components configured via spring using a VMTransport in our connection factory.
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <beans  xmlns:jms="http://servicemix.apache.org/jms/1.0">
>       <jms:consumer service="xsite:jms-consumer"
>                                     endpoint="myConsumer"
>                                     targetService="impl:eip-pipeline"
>                                     targetEndpoint="transformXML"
>                                     destinationName="queue.input"
>                                     connectionFactory="#connectionFactory"
>                                     cacheLevel="3"
>                                     transacted="jms" />
>       <jms:connectionFactory brokerURL="vm://localhost"/>
> </beans>
> {code}
> What we see is a small memory leak related to advisory messages where the broker MemoryUsage is incremented slowly over time.  After investigating this further we saw that certain messages references were being incremented more than they were decremented.  As a result the method org.apache.activemq.usage.MemoryUsage.decreaseUsage() was not being called when needed inside the org.apache.activemq.command.Message.decrementReferenceCount() due to the referenceCount being invalid.  AFter a while, 2days or so, with our configuration producerFlowControl would stop the flow of messages (invalidly) due to this problem.

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