Gary Tully created AMQ-7302:
-------------------------------

             Summary: JMX operation removeMessage(messageID) is not completing 
and leading to high CPU usage
                 Key: AMQ-7302
                 URL: https://issues.apache.org/jira/browse/AMQ-7302
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMX
    Affects Versions: 5.15.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.16.0


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.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to