[ https://issues.apache.org/jira/browse/AMQ-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-6690. ----------------------------- Resolution: Fixed I considered throwing an exception but I think it is safer to retain the existing behaviour and report via the return code > 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)