[
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.
