[jira] [Commented] (AMQ-7302) JMX operation removeMessage(messageID) is not completing and leading to high CPU usage

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926511#comment-16926511 ] 

ASF subversion and git services commented on AMQ-7302:
------------------------------------------------------

Commit 501d55337adaecdad7fb6311afcf618503a9e9b5 in activemq's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=501d553 ]

AMQ-7302 - make jmx ops that pageIn aware of cursor memory limits to avoid excessive looping, fix and test


> 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
>            Priority: Major
>             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)