[
https://issues.apache.org/jira/browse/AMQ-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015622#comment-16015622
]
ASF subversion and git services commented on AMQ-6678:
------------------------------------------------------
Commit acab282d9cb348cfc608ee405de4f9d3566698cc in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=acab282 ]
[AMQ-6678] sync destructive queue view mbean (jmx) operations such that
concurrent calls see consistent state
> 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)
