[
https://issues.jboss.org/browse/WFCORE-1561?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1561:
------------------------------------------
[~harald.pehl] I agree with John in that the return value should include the host data,
but I'm concerned that fixing it might impact the console, so I wanted to give you an
FYI. Do you have any concerns?
It looks like the problem relates to the fact that the host+server is fully specified. For
example this analogous operation has the behavior John reports:
{code}
[domain@localhost:9990 /]
/host=master/server=server-one/subsystem=logging/logger=*:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => [
{
"address" => [
("subsystem" => "logging"),
("logger" => "com.arjuna")
],
"outcome" => "success",
"result" => {
"category" => "com.arjuna",
"filter" => undefined,
"filter-spec" => undefined,
"handlers" => undefined,
"level" => "WARN",
"use-parent-handlers" => true
}
},
. . . .
{code}
But this one that uses server=* instead of server=server-one works as expected:
{code}
[domain@localhost:9990 /]
/host=master/server=*/subsystem=logging/logger=*:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => [
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("subsystem" => "logging"),
("logger" => "com.arjuna")
],
"outcome" => "success",
"result" => {
"category" => "com.arjuna",
"filter" => undefined,
"filter-spec" => undefined,
"handlers" => undefined,
"level" => "WARN",
"use-parent-handlers" => true
}
},
. . . .
{code}
read-resource responds with incorrect address when going through host
controller
--------------------------------------------------------------------------------
Key: WFCORE-1561
URL:
https://issues.jboss.org/browse/WFCORE-1561
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.1.0.Final
Reporter: John Mazzitelli
Assignee: Brian Stansberry
I have a typical small domain setup: one master host controller (aka domain controller)
and one slave host controller with "server-one" and "server-two"
servers.
I need to discover things running in those two servers (server-one and server-two). As
part of the discovery, I invoke read-resource operations via the management interface -
for example, to discover all the datasources in server-one:
/host=slave/server=server-one/subsystem=datasources/data-source=*/:read-resource(include-runtime=true)
For each returned datasource, I need to know that datasource's full address. The
problem is, I do not get the full address. Instead, the CLI returns the following partial
address:
{
"outcome" => "success",
"result" => [{
"address" => [
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
],
"outcome" => "success",
"result" => {
"allocation-retry" => undefined,
...and the rest of the properties for the ExampleDS datasource...
}
}
}]
}
The address should be the full address of:
"address" => [
("host" => "slave"),
("server" => "server-one"),
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
],
NOTE! This problem occurs both when I connect to the domain controller and when I connect
to the slave host controller - it doesn't matter, the CLI returns the same erroneous
address if connected to either one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)