-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.0.8.GA, 7.1.0.CR2
-
None
In Wildfly, a command such as this with a non-existent path returns success instead of failed:
/host=master/server=nonExistant:read-attribute(name=runtime-configuration-state) { "outcome" => "success", "result" => "stopped" }
Where as in EAP 6.4:
[domain@localhost:9999 /] /host=master/server=server-NOT-EXIST:read-attribute(name=server-state) Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-NOT-EXIST") ]"
- clones
-
JBEAP-13389 [GSS](7.1.z) Management returning success for read-attribute on non-existent path
- Closed