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

Posted to issues@activemq.apache.org by "Jean-Marc Borer (Jira)" <ji...@apache.org> on 2019/10/30 16:41:00 UTC

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

     [ https://issues.apache.org/jira/browse/AMQ-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Marc Borer updated AMQ-7272:
---------------------------------
    Priority: Blocker  (was: Major)

> 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: Jean-Marc Borer
>            Priority: Blocker
>
> 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
(v8.3.4#803005)