[jboss-jira] [JBoss JIRA] (WFCORE-307) When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
[
https://issues.jboss.org/browse/WFCORE-307?page=com.atlassian.jira.plugin...
]
Brian Stansberry reopened WFCORE-307:
-------------------------------------
I'm reopening this due to the WFCORE-1639 issue.
Another possible approach is to have the Stage.RUNTIME add handlers for the management
interface resources, during boot only, add a Stage.VERIFY step to confirm the services are
UP. VERIFY runs after MSC stability is reached. If the service isn't up they can call
context.setRollbackOnly(). I believe that should overrule the usual
rollback-on-runtime-failure=false behavior of the boot time OperationContext and result in
the op returning ResultAction.ROLLBACK, which will cause the boot to fail.
Basically the resources themselves can verify that they came up.
When Wildfly fails with JBAS015810: failed to resolve interface
management, it should terminate.
------------------------------------------------------------------------------------------------
Key: WFCORE-307
URL: https://issues.jboss.org/browse/WFCORE-307
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Jay SenSharma
Assignee: ehsavoie Hugonnet
Fix For: 3.0.0.Alpha2
- 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 was sent by Atlassian JIRA
(v6.4.11#64026)