[jboss-jira] [JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api

[Brian Stansberry (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644822#comment-13644822 ] 

Brian Stansberry commented on WFLY-11127:
-----------------------------------------

But it probably won't work anyway once you correct that, since the undertow one doesn't work. I believe this has something to do with 'server' appearing as the key in two elements in the address.  I have a vague recollection of some fix related to that kind of thing, although my vague feeling doesn't put the fix in the ~ 6 months since we released WildFly 12. And it's interesting it seems to not be a problem with whatever this management GUI is. Which based on the syntax I assume is the CLI or some other JBoss Remoting based mechanism.

Can you try this with WF 14?

> Can not get activemq and undertow subsystem data from HTTP management api
> -------------------------------------------------------------------------
>
>                 Key: WFLY-11127
>                 URL: https://issues.jboss.org/browse/WFLY-11127
>             Project: WildFly
>          Issue Type: Bug
>          Components: Management, Web (Undertow)
>    Affects Versions: 12.0.0.Final
>            Reporter: Toni Moreno
>            Assignee: Jeff Mesnil
>            Priority: Critical
>
> As described in  https://github.com/wildfly/wildfly/issues/11309
> I can not get  some subsystems info data with the HTTP management API working with
>  
> ======================================
>               "product-version" => "12.0.0.Final",
>                 "product-community-identifier" => "Product",
>                 "product-home" => "/usr/local/wildfly-12.0.0.Final",
>                 "standalone-or-domain-identifier" => "HOST_CONTROLLER",
>                 "host-operating-system" => "Debian GNU/Linux 8 (jessie)}}
> ===============
> This the a activemq POST request with curl and its error
> ---------8<------------------------------------------8<-----------------------
> root at snmpcoldev01:~#  curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin 
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 103
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> "java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR
> --------->8------------------------------------------>8-----------------------
> And this the query with the GUI client
> [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/5883405/40872423-3a374802-664e-11e8-915e-c1dc7225804a.jpg]
> Also with undertow subsystem
> ---------8<------------------------------------------8<-----------------------
> root at snmpcoldev01:~#  curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin 
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 302
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> {
>     "outcome" : "failed",
>     "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n    (\"host\" => \"master\"),\n    (\"server\" => \"default-server\"),\n    (\"subsystem\" => \"undertow\"),\n    (\"http-listener\" => \"default\")\n]",
>     "rolled-back" : true
> }
> --------->8------------------------------------------>8-----------------------
> Here Image of the GUI management query.
> [jboss_undertow_listener_gui_query|https://user-images.githubusercontent.com/5883405/40872494-56062e4e-664f-11e8-8436-4d7095293974.jpg]



--
This message was sent by Atlassian Jira
(v7.12.1#712002)