Bug 1324073 - The set of operations provided by JON for ActiveMQ Artemis Server Runtime resource is not defined in EAP7
Summary: The set of operations provided by JON for ActiveMQ Artemis Server Runtime res...
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-04-05 13:00 UTC by Filip Brychta
Modified: 2016-06-06 18:57 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
mdb deployment (10.70 KB, application/zip)
2016-04-05 13:00 UTC, Filip Brychta
no flags Details

Description Filip Brychta 2016-04-05 13:00:39 UTC
Created attachment 1143834 [details]
mdb deployment

Description of problem:
JON defines the same operation list for "ActiveMQ Artemis" and "ActiveMQ Artemis Server Runtime" but the list is not the same on EAP7 side. So when invoking given operation it fails with No operation named 'get-connectors-as-json' exists

Version-Release number of selected component (if applicable):
JON3.3.5 with eap plugin pack update04-DR02

How reproducible:
Always

Steps to Reproduce:
1. deploy attached mdb.war
2. navigate to EAP 7 -> Deployments->mdb.war->messaging-activemq->default (ActiveMQ Artemis Server Runtime)-> Operations
3. invoke Get Connectors as JSON

Actual results:
Operation fails with  No operation named 'get-connectors-as-json' exists

Expected results:
Not sure if the problem is on EAP7 side (missing operations) or incorrect operation list on JON side.

Additional info:
Output from jboss-cli:
[standalone.0.1:10090 /] /deployment=mdb.war/subsystem=messaging-activemq/server=default:read-operation-names
{
    "outcome" => "success",
    "result" => [
        "list-add",
        "list-clear",
        "list-get",
        "list-remove",
        "map-clear",
        "map-get",
        "map-put",
        "map-remove",
        "query",
        "read-attribute",
        "read-attribute-group",
        "read-attribute-group-names",
        "read-children-names",
        "read-children-resources",
        "read-children-types",
        "read-operation-description",
        "read-operation-names",
        "read-resource",
        "read-resource-description",
        "undefine-attribute",
        "whoami",
        "write-attribute"
    ]
}


Operations are defined on ActiveMQ Artemis (EAP 7 -> Deployments->subsystems->messaging-activemq->default) correclty:
[standalone.0.1:10090 /] /subsystem=messaging-activemq/server=default:read-operation-names
{
    "outcome" => "success",
    "result" => [
        "add",
        "close-connections-for-address",
        "close-connections-for-user",
        "close-consumer-connections-for-address",
        "commit-prepared-transaction",
        "export-journal",
        "force-failover",
        "get-address-settings-as-json",
        "get-connectors-as-json",
        "get-last-sent-message-id",
        "get-roles",
        "get-roles-as-json",
        "get-session-creation-time",
        "import-journal",
        "list-add",
        "list-all-consumers-as-json",
        "list-clear",
        "list-connection-ids",
        "list-connections-as-json",
        "list-consumers-as-json",
        "list-get",
        "list-heuristic-committed-transactions",
        "list-heuristic-rolled-back-transactions",
        "list-prepared-transaction-details-as-html",
        "list-prepared-transaction-details-as-json",
        "list-prepared-transaction-jms-details-as-html",
        "list-prepared-transaction-jms-details-as-json",
        "list-prepared-transactions",
        "list-producers-info-as-json",
        "list-remote-addresses",
        "list-remove",
        "list-sessions",
        "list-sessions-as-json",
        "list-target-destinations",
        "map-clear",
        "map-get",
        "map-put",
        "map-remove",
        "query",
        "read-attribute",
        "read-attribute-group",
        "read-attribute-group-names",
        "read-children-names",
        "read-children-resources",
        "read-children-types",
        "read-operation-description",
        "read-operation-names",
        "read-resource",
        "read-resource-description",
        "remove",
        "reset-all-message-counter-histories",
        "reset-all-message-counters",
        "resolve-address-setting",
        "rollback-prepared-transaction",
        "undefine-attribute",
        "whoami",
        "write-attribute"
    ]
}

Comment 1 Michael Burman 2016-04-08 13:16:02 UTC
Fixed in the master:

commit d14b6d67a3607bee21d4c0e785f60188c1264a2c
Author: Michael Burman <miburman>
Date:   Fri Apr 8 16:15:28 2016 +0300

    [BZ 1324073] Fixed Runtime ActiveMQ Subsystem configuration


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