6:44 a.m.
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
7:11 a.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Kabir Khan commented on AS7-3114:
---------------------------------
This should perhaps be settable up by a command-line argument, rather than automagic?
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
7:31 a.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on AS7-3114:
------------------------------------
Some products come without the Console. The best would be some default option coming out
of Maven via a profile with a command-line override. Then there would be no automagic
needed.
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
7:34 a.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
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
9:41 a.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3114:
---------------------------------------
Another factor in the equation is that whether or not to have the console needs to be a
configurable attribute, probably on the http management interface element. It's quite
reasonable that people using AS 7 / EAP will want to use the HTTP management connector but
not run a console.
So you have a matrix:
One access: Is the console available? (yes/no)
Other access: Does user want console? (yes/no/didn't say)
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
12:27 p.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-3114:
----------------------------------
Fix Version/s: 7.1.0.Final
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
Fix For: 7.1.0.Final
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
2:54 p.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-3114:
-------------------------------------
Assignee: Tomaz Cerar (was: Brian Stansberry)
Tomaz, can you look into this one? There are two aspects:
1) Add a non-required boolean config attribute the the
<management-interfaces><http-interface> element to allow users to disable the
console. Default is true.
2) Detect the absence of the module that provides the console, and deal with that absence
appropriately.
How to deal with the absence of the console is an open question. One thought I had was to
throw an exception if the config attribute was actually set to "true". If the
config attribute is undefined or false then deal with it using ConsoleMode.NO_CONSOLE.
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: Tomaz Cerar
Fix For: 7.1.0.Final
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
4:33 p.m.
[
https://issues.jboss.org/browse/AS7-3114?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar commented on AS7-3114:
----------------------------------
Now there is new "console-enabled" attribute that controls the behavior of
console.
if console-enabled is not set in xml or in console it defaults to true and old behavior.
if set to false it will set consoleMode to ConsoleMode.NO_CONSOLE.
Non existing console module now just warns that console is missing instead of throwing the
exception.
This could be improved by setting console-enabled to false, so that next boot it would not
even try to load the console.
Attribute is also present at path
/core-service=management/management-interface=http-interface and you can control the
console run-time without restarting the server.
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: Tomaz Cerar
Fix For: 7.1.0.Final
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
5253
days inactive
5280
days old
7 comments
8 participants
participants (8)
-
Brian Stansberry (Assigned) (JIRA) -
Brian Stansberry (Commented) (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Carlo de Wolf (Commented) (JIRA)
-
Carlo de Wolf (Created) (JIRA)
-
Darran Lofthouse (Commented) (JIRA)
-
Kabir Khan (Commented) (JIRA)
-
Tomaz Cerar (JIRA)