Description of problem: When I access runtime information of a server which is turned off an Error message is shown in message box regarding the resource not being registered Version-Release number of selected component (if applicable): EAP 6 ER4 How reproducible: Steps to Reproduce: 1. connect via admin console 2. stop one of the servers and change under runtime the server to the stopped one 3. try to access any of the information under server status Actual results: Error message with DMR/CLI output informing that the resource definition is not registered Expected results: Warning message that the server is stopped => unable to get requested info Additional info:
For example when accessing in Runtime the Environment part: Failed to create security context for environment, fallback to temporary read-only context Unexpected HTTP response: 500 Request { "operation" => "composite", "address" => [], "steps" => [{ "address" => [ ("host" => "master"), ("server" => "server-two"), ("core-service" => "platform-mbean"), ("type" => "runtime") ], "operation" => "read-resource-description", "recursive-depth" => 2, "access-control" => "trim-descriptions", "operations" => true }] } Response Internal Server Error { "outcome" => "failed", "failure-description" => "JBAS014883: No resource definition is registered for address [ (\"host\" => \"master\"), (\"server\" => \"server-two\"), (\"core-service\" => \"platform-mbean\"), (\"type\" => \"runtime\") ]", "rolled-back" => true }
This also affect creation of security context in case of rbac - thus every access to any runtime page will throw and Error for not started server. Rising severity as we don't want our customers to see an error message on every page.
Heiko Braun <ike.braun> updated the status of jira HAL-275 to Resolved
Heiko Braun <ike.braun> updated the status of jira HAL-275 to Reopened
Included in HAL 2.0.5.Final
verified 6.2.0.ER7