Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000BeaCj&sfdc.override=1 Steps to Reproduce: Have a host controller (can be the DC itself) with one server up and running. Modify manually the host.xml, introducing a typo, for example remove a "<" from tag. From the CLI, execute: /host=master:reload The result is the host controller AND the server process quitting. It would seem reasonable that the "reload" at least checks the new xml for schema errors and rejects it. project_key: JBPAPP6 The command :reload does not check the new configuration, and will cause server crashes if that config is broken
Link: Added: This issue Cloned from AS7-5976
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public
First, editing the xml file underneath a running server is a bad practice we shouldn't attempt to support. Second, it does check the xml – when it parses it. The only reason to do basic validation before shutting down the old services is to support people trying to manually edit the xml under a running server. For which, see above.
reopening as per Brian's request
Is this item targeted to EAP 6.1.0 ? If yes, please add 'jboss-eap-6.1.0' flag.
This will be in EAP 6.1.0. It was fixed in upstream quite a while ago.
Unless I'm doing something wrong the behavior in ER3 is exactly the same as described in bug report. After performing /host=master:reload with the corrupted host.xml server process will quit with ConfigurationPersistenceException. Changing status back to assigned
See my comment on Dec 10 on AS7-5976: "The critical task here is to validate the behavior is correct if the reload operation includes the restart-servers=false parameter. In that case the user's intent is the servers remain unaffected by the reload, so having the PC terminate due to failure is incorrect. Having the PC terminate due to failure to reload the HC is ok if no servers are running, as a PC with no servers and an unusable HC is of little value." So, use /host=master:reload(restart-servers=false) to check the behavior if you don't want servers affected.
Verified on EAP 6.1.0 ER4. Corrupting the host.xml and calling /host=master:reload(restart-servers=false) won't affect running servers. PC without running servers is terminated.
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html