JMX subsystem can't be removed on the first calling of CLI command /subsystem=jmx:remove(). However if I call this command again it is successfully removed. Steps to reproduce: 1) (maybe only optional) remove remoting-connector from JMX: /subsystem=jmx/remoting-connector=jmx:remove() 2) remove JMX subsystem: /subsystem=jmx:remove() it fails with: { "outcome" => "failed", "failure-description" => "JBAS014762: Removing services has lead to unsatisfied dependencies: Service jboss.mbean.server was depended upon by service jboss.ws.config", "rolled-back" => true } and server log in console: INFO [org.jboss.as.controller] (management-handler-thread - 1) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.mbean.server (missing) dependents: [service jboss.ws.config] 3) try to remove JMX subsystem again: /subsystem=jmx:remove() leads to: {"outcome" => "success"} and JMX subsystem is removed. I think removing of subsystem should be successful after the first calling of command /subsystem=jmx:remove().
We don't support removing subsystems that provide services that are depended upon by other subsystems. There are many cases where trying this will result in failure. The fact that it works that second time needs investigation, since it doesn't seem like it should.
Brain, thanks for the clarification. I tried procedure from Administration and Configuration Guide describing removing this subsystem (Example 10.17. Remove the JMX Subsystem in 10.7.7. Disable Remote Access to the JMX Subsystem). In case we don't support this issue I fill documentation bugzilla about removing this example from the Guide.
Using this one as downstream for WFLY-3566. Note: BZ1088348 is one Ondra did for documentation.
Backport: https://github.com/jbossas/jboss-eap/pull/1547
Verified in EAP 6.4.0.DR1.1.