[jboss-jira] [JBoss JIRA] (WFLY-9202) /subsystem=messaging-activemq:remove fails when not run in batch

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil moved JBEAP-12610 to WFLY-9202:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-9202  (was: JBEAP-12610)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                           (was: JMS)
    Affects Version/s: 11.0.0.Beta1
                           (was: 7.1.0.ER3)


> /subsystem=messaging-activemq:remove fails when not run in batch
> ----------------------------------------------------------------
>
>                 Key: WFLY-9202
>                 URL: https://issues.jboss.org/browse/WFLY-9202
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 11.0.0.Beta1
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> Calling the following command in ER3 fails (passed with reload required in ER2.2):
> {noformat}
> /subsystem=messaging-activemq:remove()
> {noformat}
> {noformat}
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.messaging-activemq.client-thread-pool was depended upon by service jboss.messaging-activemq.default.jms.manager",
>     "rolled-back" => true,
>     "response-headers" => undefined
> }
> {noformat}
> The command now needs to be run in batch to succeed. I'm tempted to call this a blocker due to management operation backward compatibility (breaks scripts which don't run the remove operation in batch), [~okalman] WDYT?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)