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

Queue's copyMatchingMessages effects maxPageSize in error

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.15.0
    • Fix Version/s: 5.16.0
    • Component/s: Broker
    • Labels:
      None

      Description

      The copyMatchingMessages jmx op toggles the destination maxPageSize attribute. It should not do this b/c it is not thread safe and can effect other paging operations like dispatch and purge.
      In addition, concurrent calls to copyMatchingMessages can leave the value at queueDepth.
      For large queues, have the maxPageSize == queueDepth means we try and page in the entire queue, leading to an OOM.
      For non persistent brokers or where all messages are cached, it is sensible to attempt to reference all of the messages in the queue, however in general respecting the maxPageSize is advisable.

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: