[ https://issues.jboss.org/browse/WFCORE-3897?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-3897: ----------------------------------- Note down Brian's reply in email and analysis: {quote}It's a bug that the host starts at all with that misconfiguration. If it's started --admin-only it should boot, to give an admin a chance to correct the misconfiguration. But with this one it boots even not in admin-only. Can you file a JIRA?{quote} The HC only check required server group existence in server start. In this case, servers are configured to auto-start="false", no error indicates any misconfiguration. {quote}You can invoke a management write op without restarting in --admin-only, but it has to be one that corrects all issues. If you have several invalid attributes (e.g. two server-config resources with invalid group attributes) then you need to correct them all in one op, using a batch.{quote} In admin only mode, use CLI to run example like: {code:xml} [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /server-group=main-server-group:add(profile=full,socket-binding-group=full-sockets) [domain@localhost:9990 / #] /system-property=foo:add(value=bar) [domain@localhost:9990 / #] run-batch {code} {quote}It's not a bug that other write ops fail. The system validates its config as part of any write op and if it finds an inconsistent config it will fail and roll back the op.{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)