[jboss-jira] [JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-156:
-----------------------------------------

Turns out the fact these interface services aren't ON_DEMAND was a bug in the WFCORE-102 patch. The patch removed that setting.

> Defer the WFLY-184 validation until service start
> -------------------------------------------------
>
>                 Key: WFCORE-156
>                 URL: https://issues.jboss.org/browse/WFCORE-156
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller.
> This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required.
> Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)