[jboss-jira] [JBoss JIRA] (AS7-2218) Delay management-console startup until the server is started

[Heiko Braun (JIRA)]

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

Heiko Braun commented on AS7-2218:
----------------------------------

yes, this approach would work in both cases:

a) console not loaded, but it will be
b) it is loaded and does operate 

in either case the regular http request to load the console should succeed and 503 on subsequent operations will be handled gracefully by the console itself.


as for the general usage (other clients): IMO the 503 is the best way to deal with it and conforms with the http specification. The difference between native and http protocol are by design. not much to worry about, if you ask me.

                
> Delay management-console startup until the server is started
> ------------------------------------------------------------
>
>                 Key: AS7-2218
>                 URL: https://issues.jboss.org/browse/AS7-2218
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.0.2.Final
>         Environment: Linux myhost 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 i686 i386 GNU/Linux
> Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
> java version "1.6.0_23"
> Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
> Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode)
>            Reporter: Anatoly Kupriyanov
>            Assignee: Heiko Braun
>            Priority: Critical
>             Fix For: 7.1.2.Final-redhat1
>
>         Attachments: AS7-2218-1.0.war, AS7-2218.zip
>
>
> Management console stops working after I deploy a .war file. One way to fix - manually edit the standalone.xml file and remove the <deployments> section.
> Console displays "No manageable subsystems exist." and all fails. There is an error message:
> {quote}
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
>     "operation" => "read-children-resources",
>     "address" => [("subsystem" => "datasources")],
>     "child-type" => "xa-data-source"
> }
> Response
> Internal Server Error
> {
>     "outcome" => "failed",
>     "failure-description" => "Operation handler failed: java.util.NoSuchElementException: \"subsystem\" => \"datasources\"",
>     "rolled-back" => true
> }
> {quote}
> log has:
> {quote}
> 13:52:03,200 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 1) Operation ("read-children-resources") failed - address: ([("subsystem" => "datasources")]): java.util.NoSuchElementException: "subsystem" => "datasources"
>         at org.jboss.as.controller.registry.BasicResource.requireChild(BasicResource.java:95) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.ModelControllerImpl$RootResource.requireChild(ModelControllerImpl.java:423) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:764) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadChildrenResourcesOperationHandler.execute(GlobalOperationHandlers.java:487) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:353) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:350) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:353) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:209) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:199) [jboss-as-controller-7.0.2.Final.jar:7.0.2.Final]
>         at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:188)
>         at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:123)
>         at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
>         at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80)
>         at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
>         at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:689)
>         at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
>         at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:661)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
>         at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
>         at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira