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

Message content can be cleared by mistake when isReduceMemoryFootprint is enabled

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.13.2
    • Fix Version/s: 5.13.3, 5.14.0
    • Component/s: Broker
    • Labels:
      None

      Description

      In a Queue when isReduceMemoryFootprint is enabled the message state should be cleared after persisting to the store. The idea is that once the data is marshalled into its byte content we can clear out the properties, text, etc to free up memory.

      The problem is that when concurrent dispatch is enabled, messages are added to the store asynchronously and queued up. There is a race condition because it's possible for the state to be cleared before the store has a chance to process the message so that when it gets to it, it will be null. This is most notable when using the VM transport as messages with null content will get dispatched.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cshannon Christopher L. Shannon
                Reporter:
                cshannon Christopher L. Shannon
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: