Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-7272

Fanout transport has a memory leak

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Blocker
    • Resolution: Unresolved
    • 5.15.9
    • None
    • JMS client
    • None

    Description

      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.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            jmborer Jean-Marc Borer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: