You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "jmborer (JIRA)" <ji...@apache.org> on 2019/08/08 14:47:00 UTC

[jira] [Created] (AMQ-7272) Fanout transport has a memory leak

jmborer created AMQ-7272:
----------------------------

             Summary: Fanout transport has a memory leak
                 Key: AMQ-7272
                 URL: https://issues.apache.org/jira/browse/AMQ-7272
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.15.9
            Reporter: jmborer


When using the fanout transport we had memory leaks. Actually, the ConnectionStateTracker class retains all ActiveMQTextMessages and are never released.

In FanoutTransport.oneway on line 405, the command is tracked by a stateTracker object. The latter stores it in a map in ConnectionStateTracker.processMessage on line 541. However this map in never cleared and not used anyway by the FanoutTransport. 

It is possible to the disable the message tracking by setting it to false.

We tried a local version of the ActiveMQ Client where we set the  ConnectionStateTracker.setTrackMessages(false).

We have no more memory leaks, but are unsure about side effects. In our case, there are none because we use JMS very simply.

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)