You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "teddy (JIRA)" <ji...@apache.org> on 2015/10/12 05:57:05 UTC

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

teddy created AMQ-6008:
--------------------------

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