Bug 1322811 - EAP7 - messaging-activemq subsystem is not discovered in full profile of domain controller
Summary: EAP7 - messaging-activemq subsystem is not discovered in full profile of doma...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 7
Version: JON 3.3.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER01
: One-off release
Assignee: Michael Burman
QA Contact: Filip Brychta
URL:
Whiteboard:
Depends On:
Blocks: 1314853
TreeView+ depends on / blocked
 
Reported: 2016-03-31 11:26 UTC by Filip Brychta
Modified: 2016-06-06 18:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 18:58:16 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Filip Brychta 2016-03-31 11:26:53 UTC 
Description of problem:
EAP7 full profile contains messaging-activemq subsystem but it's not discovered by JON.
From jboss-cli:
[domain.0.1:8990 /] /profile=full/subsystem=messaging-activemq:read-resource
{
    "outcome" => "success",
    "result" => {
        "jms-bridge" => undefined,
        "server" => {"default" => undefined}
    }
}

subsystem is there but it's not discovered by JON.


Version-Release number of selected component (if applicable):
JON 3.3.5 + eap plugin pack update04-DR01

How reproducible:
Always

Steps to Reproduce:
1. import domain EAP 7 Domain controller resource to JON inventory
2. go to profiles->full->subsystems


Actual results:
messaging-activemq subsystem is not there

Expected results:
messaging-activemq subsystem should be there

Additional info:
messaging-activemq subsystem is discovered correctly in eap 7 standalone
Comment 1 Michael Burman 2016-04-04 08:20:22 UTC 
Fixed in the master:

commit da4682f49f73c02fd6f4e03f97e23c8765f07b86
Author: Michael Burman <miburman>
Date:   Mon Apr 4 11:19:42 2016 +0300

    [BZ 1322811] Fix path of ActiveMQMessaging (Profile)
Note You need to log in before you can comment on or make changes to this bug.