[
https://issues.apache.org/jira/browse/AMQ-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956154#comment-14956154
]
teddy commented on AMQ-6008:
----------------------------
My test case is :
1. using leveldb and messages are set persistent
2. loop send messages to topicA and loop draw messages from qA1 and qA2
2. with jmx remote enable, using jconsole to monitor the memory
3. the old gen keep increasing, each full gc cycles the only portion of memory
free. The old gen stacks up.
Once I set the concurrentSend="true" , and re-do the above, at each full gc
cycles, almost all memory free.
> Memory leak in using composite destinations
> -------------------------------------------
>
> Key: AMQ-6008
> URL: https://issues.apache.org/jira/browse/AMQ-6008
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.11.1
> Reporter: teddy
> Priority: Minor
>
> I have found that when using composite destinations, predefined in
> activemq.xml as below
> <compositeTopic name="topicA" forwardOnly="false" >
> <forwardTo>
> <queue physicalName="qA1" />
> <queue physicalName="qA2" />
> </forwardTo>
> </compositeTopic>
> when forward to more than one queue, there will be memory leak , and stack
> up, cannot release in full GC cycles and finally run out of memory
> <compositeTopic name="topicA" forwardOnly="false" concurrentSend="true">
> <forwardTo>
> <queue physicalName="qA1" />
> <queue physicalName="qA2" />
> </forwardTo>
> </compositeTopic>
> but if the concurrentSend is explicitly set as "true" , everything will be
> fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
