You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2017/05/18 11:41:04 UTC

[jira] [Resolved] (AMQ-6678) Move/Retry (destructive) Queue JMX operations need synchronization

     [ https://issues.apache.org/jira/browse/AMQ-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-6678.
-----------------------------
    Resolution: Fixed

fix and test added.

> Move/Retry (destructive) Queue JMX operations need synchronization
> ------------------------------------------------------------------
>
>                 Key: AMQ-6678
>                 URL: https://issues.apache.org/jira/browse/AMQ-6678
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMX
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.0
>
>
> concurrent calls to move selector matching messages from one queue to another or any wildcard type destructive JMX operation can break on concurrent invocation.
> The move results in duplicates in the journal (waste of space) and incorrect return counts due to inflight messages being visible in error.
> Two jmx consoles is enough to cause problems.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)