Bug 968815 - Cannot remove jgroups subsystem from CLI by saying "JBAS014807: Management resource ... not found"
Summary: Cannot remove jgroups subsystem from CLI by saying "JBAS014807: Management re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.1.1
Assignee: Brian Stansberry
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 03:39 UTC by Osamu Nagano
Modified: 2018-12-01 14:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:20:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1437 0 Major Closed Cannot remove JGroups subsystem from managed domain via CLI 2018-11-27 13:57:33 UTC

Description Osamu Nagano 2013-05-30 03:39:59 UTC
Description of problem:
In EAP 6.1 domain mode, try to create a new profile from scratch in CLI.  You can add jgroups subsystem but you cannot remove it with an error message.
In standalone mode and both modes of EAP 6.0.1, you can successfully remove it.


Steps to Reproduce:
1. Start EAP 6.1 in domain mode.  The default domain.xml is sufficient.
2. Connect to the DC by CLI.
3. Execute the following commands in CLI.
--
[domain@localhost:9999 /] /profile=test:add()
[domain@localhost:9999 /] /profile=test/subsystem=jgroups:add(default-stack=udp)
[domain@localhost:9999 /] /profile=test/subsystem=jgroups:remove()
--

Actual results:
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"jgroups\")]' not found"},
    "rolled-back" => true
}

Expected results:
{
    "outcome" => "success",
    "result" => undefined,
    "server-groups" => undefined
}

Comment 2 Brian Stansberry 2013-06-01 15:38:33 UTC
This same problem exists in upstream. There's been some discussion that the patch for https://issues.jboss.org/browse/WFLY-439 fixes this, but it doesn't (and shouldn't, as it's unrelated.)

The problem is in JGroupsSubsystemRemove:

ModelNode removeSubsystem = Util.createOperation(REMOVE, PathAddress.pathAddress(JGroupsExtension.SUBSYSTEM_PATH));
        context.addStep(removeSubsystem, new OriginalSubsystemRemoveHandler(), OperationContext.Stage.MODEL, true);

That PathAddress.pathAddress(JGroupsExtension.SUBSYSTEM_PATH) is incorrect in a managed domain, as it doesn't include the profile element. It's correct in a standalone server.

Easy fix.

Comment 4 Petr Kremensky 2013-06-19 09:08:26 UTC
Verified on EAP 6.1.1 ER1

Comment 5 Scott Mumford 2013-08-20 02:43:38 UTC
Added a draft release note for the 6.1.1 RN document. Please review for technical accuracy and comment on any problems.

Comment 6 Brian Stansberry 2013-08-20 05:37:11 UTC
Looks fine, Scott.


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