[jboss-jira] [JBoss JIRA] (WFCORE-3897) Host starts with server assigned to non-existent server group

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585906#comment-13585906 ] 

Brian Stansberry commented on WFCORE-3897:
------------------------------------------

[~soul2zimate] Re:

"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."

What's odd to me is that the capability reference at https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/main/java/org/jboss/as/host/controller/resources/ServerConfigResourceDefinition.java#L115 is not being validated at the end of boot.  Capability references should be validated regardless of whether a server is started. The logic that validates the model can't know and shouldn't care whether the server is configured to start.

That capability reference is checked after boot, which is why write ops start to fail. So I think it's probably something in the logic during HC boot that disables some reference checks until both the host.xml model and domain.xml model are present. When only host.xml stuff is present (i.e. boot has parsed the host.xml file but the domain.xml part isn't ready yet) then some capability refs checks are turned off. But IRRC the idea was once the domain model was available the checks would be done.  The "PartialModelIndicator" at https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/main/java/org/jboss/as/host/controller/DomainModelControllerService.java#L244 is meant to control whether this check happens.



> Host starts with server assigned to non-existent server group
> -------------------------------------------------------------
>
>                 Key: WFCORE-3897
>                 URL: https://issues.jboss.org/browse/WFCORE-3897
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 5.0.0.CR1
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>
> Configuring a host with:
>  <server name="server-one" group="main-server-group" auto-start="false"/>
>         <server name="server-two" group="main-server-group" auto-start="false">
>             <socket-bindings port-offset="150"/>
>         </server>
> And no server-goup with that name in the domain.xml, the host starts and all management operations fail.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)