[jboss-jira] [JBoss JIRA] (WFLY-5125) DestroyQueue management method does not delete the jms-queue object

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil resolved WFLY-5125.
-------------------------------
    Resolution: Won't Fix


Using Artemis MBeans directly by calling JMSServerControl.destroyQueue means you bypass WildFly management API.
It is not possible to keep a consistent management view if you bypass the API.

If you want to destroy a queue using JMX, the MBeans to use are under the jboss.as domain. If you use those, the management configuration will be updated as well as its XML file.


> DestroyQueue management method does not delete the jms-queue object
> -------------------------------------------------------------------
>
>                 Key: WFLY-5125
>                 URL: https://issues.jboss.org/browse/WFLY-5125
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Beta1
>            Reporter: Erich Duda
>            Assignee: Jeff Mesnil
>            Priority: Critical
>         Attachments: standalone-full-ha.xml
>
>
> JMSServerControl.destroyQueue returns true, but the jms-queue object still exists in EAP.



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