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

JMX operation removeMessage(messageID) is not completing and leading to high CPU usage

    XMLWordPrintableJSON

    Details

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

      Description

      JMX queue move/remove/copyTo/retry ops behave badly when a queue is memory constrained. The operations loop over pageIn() but don't check for cursor being full and nothing further being paged into memory. In addition, they allow concurrent operation which thwarts the linear search.
      this can lead to excessive looping (high CPU), hanging and NPE depending on the particular JMX op.
      The loops need to short-circuit if pageIn blocks as is the norm when the cursor is memory constrained.

        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: