[jboss-jira] [JBoss JIRA] (WFLY-3264) When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-3264:
----------------------------------------

Interesting. The boot actually consists of two batches of operations, where a failure in the first should trigger an abort, while a failure in the second should not. I'm pretty certain my intent was the 'management' interface failure would cause the first set to fail, triggering abort. Not sure why it doesn't.

The first set gets the core services, particularly the management interfaces, running. Without those you can't administer and correct any problem, so the server aborts. The second set brings in all the subsystems and deployments.

The 'public' interface wouldn't be used until the second set. Triggering abort on that second set would need to be in some way configurable. I'm pretty sure there's a JIRA about that out there somewhere.
                
> When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
> ------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3264
>                 URL: https://issues.jboss.org/browse/WFLY-3264
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.1.0.CR1
>            Reporter: Jay Kumar SenSharma
>            Assignee: Brian Stansberry
>
> - When Wildfly fails with **JBAS015810: failed to resolve interface management**, it should terminate rather than dangling. 
> - When starting the Wildfly with an IP address which is non-existent, you get the error 'JBAS015810: failed to resolve interface management'.
> -The server starts, but with the error message :
> {code}
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
> 	at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> 	at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> {code}
> - Since the server could not bind to the given address and port, and neither the cli nor the admin console are enabled, the server is as good as dead. The server should exit instead of starting up with errors when this of error is seen . 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira