]
Harald Pehl commented on WFCORE-1561:
-------------------------------------
[~brian.stansberry] it turns out that we've already "fixed" that in the
console. The console tries to detect such operations and turns the relative into a fully
qualified address. Digging through that code I remember that I wanted to file an issue for
that. Seems that I forgot to do so. So thanks [~mazz] for bringing this up.
I don't have any concerns fixing this. I only need to make sure the workaround still
works with old servers w/o the fix and causes no harm otherwise.
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: Ken Wills
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.