[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Anatoly Kupriyanov updated AS7-2218: ------------------------------------ Description: 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} was: 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: 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 } log has: 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] -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Anatoly Kupriyanov updated AS7-2218: ------------------------------------ Priority: Blocker (was: Critical) -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-2218: ------------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber resolved AS7-2218. -------------------------------------- Resolution: Cannot Reproduce Bug I can't reproduce it either. I tried this on our current develoment branch as well as 7.0.2.Final. Perhaps you can check if that issues was fixed already otherwise please re-open this issue with more details. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Anatoly Kupriyanov updated AS7-2218: ------------------------------------ Attachment: AS7-2218.zip AS7-2218-1.0.war The init method of war's servlet has 60s sleep. During this period management console fails. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-2218: ------------------------------ Priority: Critical (was: Blocker) While this should block CR1, it shouldnt block beta. So I am going to drop the priority to critical for now. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-2218: ---------------------------------- Same should be true for the CLI -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-2218: ----------------------------- Component/s: (was: Console) -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2218: ---------------------------------- Fix Version/s: 7.1.1.Final (was: 7.1.0.Final) -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber commented on AS7-2218: ------------------------------------------ The title of this issue might be misleading, you can most definitely deploy .war files through the web console. The problem described here is that when you start the server, we don't expose any management information until the server is fully started (and the deployments added through the web console deployed). Which means once the server is started you should be able to use the web console without any problems. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2218: ---------------------------------- Fix Version/s: 7.1.2.Final (was: 7.1.1.Final) -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-2218: --------------------------------------- Heiko, https://github.com/bstansberry/jboss-as/tree/AS7-2284 deals with this by checking server-status before responding to a request for a console/ URL. If it is STARTING, a 503 reponse is sent, with a "Retry-After: 2" header. With that I see Firefox, Chrome and Safari wait while the server starts (I used a debugger breakpoint to delay start) and then display the usual page when start is complete. WDYT about this approach? -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-2218: ---------------------------------- The "Retry-After" seems to be ignored in all browsers I've tested. As per specification this seems to be the right way to do it, but the client has to deal with the 503 response on it's own. When requesting "/console/App.html" however, this is the responsibility of the browser implementation and beyond our reach. AFAIK the headers are completely ignored. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-2218: --------------------------------------- Re: the "Retry-After" being ignored, that's interesting. When I tested using this, I caused the server boot to block and while it would block the browser would block on my request to http://localhost:9990/console. When I let the boot finish the page would come up. I interpreted that as meaning the browser was retrying in the background. I didn't verify that's what was actually happening though. This was with Firefox, Chrome and Safari, all on my macbook. TBH, I was a bit surprised when it seemed to work; I expected the browsers to ignore the Retry-After. Anyway, if it's not working for you, that's evidence enough that it's not reliable. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] 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. -- 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

[ https://issues.jboss.org/browse/AS7-2218?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-2218: ----------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/2118 (was: https://github.com/jbossas/jboss-as/pull/2118) Component/s: Console -- 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