[jboss-jira] [JBoss JIRA] (WFCORE-1397) Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true

Brian Stansberry (JIRA) issues at jboss.org
Tue May 10 15:50:01 EDT 2016


     [ https://issues.jboss.org/browse/WFCORE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-1397:
-------------------------------------
    Fix Version/s: 2.2.0.CR1


> Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1397
>                 URL: https://issues.jboss.org/browse/WFCORE-1397
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 2.1.0.CR1
>            Reporter: Brian Stansberry
>            Assignee: Yeray Santana Borges
>            Priority: Critical
>             Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> The https://github.com/wildfly/wildfly-core/pull/1360 work added a new XnioWorker service that the HTTP interface depends on, but for a standalone server it isn't installed unless http-upgrade-enabled == true. Otherwise you see this during boot:
> {code}
>  15:43:25,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
>     ("core-service" => "management"),
>     ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
>     "jboss.serverManagement.controller.management.http is missing [jboss.serverManagement.controller.management.worker]",
>     "jboss.serverManagement.controller.management.http.shutdown is missing [jboss.remoting.management.channel.registry]"
> ]}
> 15:43:25,006 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
>     ("subsystem" => "jmx"),
>     ("remoting-connector" => "jmx")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.jmx.remoting-connector-ref is missing [jboss.remoting.endpoint.management]"]}
> 15:43:25,031 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184:    New missing/unsatisfied dependencies:
>       service jboss.remoting.endpoint.management (missing) dependents: [service jboss.jmx.remoting-connector-ref] 
>       service jboss.remoting.management.channel.registry (missing) dependents: [service jboss.serverManagement.controller.management.http.shutdown] 
>       service jboss.serverManagement.controller.management.worker (missing) dependents: [service jboss.serverManagement.controller.management.http] 
> 15:43:25,127 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
> 15:43:25,128 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
> 15:43:25,128 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.0.12.Final-redhat-1) started (with errors) in 3493ms - Started 254 of 544 services (3 services failed or missing dependencies, 369 services are lazy, passive or on-demand)
> {code}
> The problem is org.jboss.as.server.operations.HttpManagementAddHandler doesn't install the service. The HC variant of HttpManagementAddHandler does.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list