[jira] [Commented] (AMQ-6008) Memory leak in using composite destinations

["Timothy Bish (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953110#comment-14953110 ] 

Timothy Bish commented on AMQ-6008:
-----------------------------------

Do you have a test case already?  Some results from your analysis that points to an approximate location?  Anything that might help someone quickly track down what you saw?

> 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)