In 10.7.7. Disable Remote Access to the JMX Subsystem is Example 10.17. Remove the JMX Subsystem about removing JMX subsystem. However it is subsystems that provide services to other that are depended upon by other subsystems. Removing of that subsystem doesn't support (see BZ#1087711#c1) and mentioned CLI command caused failure. Whole Example 10.17. Remove the JMX Subsystem should be removed.
It's not quite correct to say that removing this subsystem isn't supported. If the other subsystems that need it aren't being used it can be removed. That said, we don't have a good mechanism for letting users analyze these inter-subsystem dependencies in EAP 6, so it's hard to provide useful documentation about how users can decide whether it's safe to remove this one, other than suggesting trial and error. So I have no argument with the suggestion to drop discussion of removing the entire subsystem.
Docs Notes ========== Disable Remote Access to the JMX Subsystem [8432, revision 690836] I commented mention of how to remove the JMX subsystem. QE Notes ======== I have removed from this section the instructions on how to remove the JMX subsystem. When the A&C Guide is next rebuilt I will move this ticket to ON_QA.
The amended text is now available for verification in revision 6.3.0-39 (or later) of the Administration and Configuration Guide [1]. [1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Disable_Remote_Access_to_the_JMX_Subsystem1
Verified in Administration and Configuration Guide in Revision 6.3.0-44.
I just take a look on BZ#1087711. Removing of JMX subsystem is possible now. For that reason fix of this BZ should be roll-backed and this BZ should be noted as Not a bug. Sorry for confusing.
Verified in Administration and Configuration Guide in Revision 6.3.0-47 and in Security Guide in Revision 6.3.0-47.