You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/31 10:28:04 UTC
[jira] [Commented] (AMQ-6690) Protect against JMX move/copy
operations onto self
[ https://issues.apache.org/jira/browse/AMQ-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030958#comment-16030958 ]
ASF subversion and git services commented on AMQ-6690:
------------------------------------------------------
Commit 8023b9ee448d2ed52c8a5c84b40dd92aae8bfc88 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=8023b9e ]
[AMQ-6690] do nothing for move/copy jmx ops that try to modify self
> Protect against JMX move/copy operations onto self
> --------------------------------------------------
>
> Key: AMQ-6690
> URL: https://issues.apache.org/jira/browse/AMQ-6690
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> The move and copy jmx operations are intended to move/copy messages to another destination. However this is not enforce and if the move/copy destination is the same queue the logs fill with duplicate warnings etc and the stats can get out of sync if the operation is repeated or concurrent.
> Best to cut this off at the pass with a return return code indicating nothing was moved/copied.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)