[jboss-jira] [JBoss JIRA] (AS7-3114) Make the console optional

[Darran Lofthouse (Commented) (JIRA)]

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

Darran Lofthouse commented on AS7-3114:
---------------------------------------

I quite like the idea of detecting the failure but still allowing the ManagementHttpServer to start - the /management context could still be potentially made available even if the console is not available.


                
> Make the console optional
> -------------------------
>
>                 Key: AS7-3114
>                 URL: https://issues.jboss.org/browse/AS7-3114
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>    Affects Versions: 7.1.0.Beta1b
>            Reporter: Carlo de Wolf
>            Assignee: Brian Stansberry
>
> Currently when booting without a console module you get the following error:
> {noformat}
> 13:32:30,936 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
> 	at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:204) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea]
> 	at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea]
> Caused by: java.io.IOException: Unable to load resource handler
> 	at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:177)
> 	at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:169) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
> 	... 5 more
> Caused by: org.jboss.modules.ModuleNotFoundException: Module org.jboss.as.console:main is not found in local module loader @5e5ad035 (roots: /home/carlo/work/jboss-as/build/target/jboss-as-7.1.0.CR1-SNAPSHOT/modules)
> 	at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> 	at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:265)
> 	at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:212)
> 	at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> 	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:194)
> 	at org.jboss.as.domain.http.server.ResourceHandler.getClassLoader(ResourceHandler.java:324)
> 	at org.jboss.as.domain.http.server.ConsoleMode$ConsoleHandler.<init>(ConsoleMode.java:99)
> 	at org.jboss.as.domain.http.server.ConsoleMode$1.createConsoleHandler(ConsoleMode.java:43)
> 	at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:175)
> 	... 6 more
> {noformat}
> It would be better to run in ConsoleMode.NO_CONSOLE if that module is not available.
> (Possibly with a friendly user message.)

--
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