Bug 1087711 - JMXSubsystemRemove is unsafe
Summary: JMXSubsystemRemove is unsafe
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR1
: EAP 6.4.0
Assignee: Kabir Khan
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 06:48 UTC by Ondrej Lukas
Modified: 2019-08-19 12:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3566 0 Major Resolved JMXSubsystemRemove is unsafe 2016-07-04 09:57:26 UTC

Description Ondrej Lukas 2014-04-15 06:48:01 UTC
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().

Comment 1 Brian Stansberry 2014-04-15 15:55:35 UTC
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.

Comment 2 Ondrej Lukas 2014-04-16 05:21:00 UTC
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.

Comment 3 Petr Kremensky 2014-07-17 10:43:41 UTC
Using this one as downstream for WFLY-3566. 

Note: BZ1088348 is one Ondra did for documentation.

Comment 5 Joe Wertz 2014-08-04 11:07:05 UTC
Backport: https://github.com/jbossas/jboss-eap/pull/1547

Comment 6 Ondrej Lukas 2014-09-22 07:15:13 UTC
Verified in EAP 6.4.0.DR1.1.


Note You need to log in before you can comment on or make changes to this bug.