[JBoss JIRA] (AS7-3114) Make the console optional
by Carlo de Wolf (Created) (JIRA)
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
14 years, 3 months
[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan updated AS7-3128:
--------------------------------
Labels: arq_qe_blocker (was: )
> Arquillian doesn't wait for the process to really end, causes problems like "port in use".
> ------------------------------------------------------------------------------------------
>
> Key: AS7-3128
> URL: https://issues.jboss.org/browse/AS7-3128
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.CR1
> Reporter: Ondrej Zizka
> Assignee: Aslak Knutsen
> Priority: Blocker
> Labels: arq_qe_blocker
>
> (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use
> (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one
> (05:54:35) dmlloyd: which may also be causing other issues
> (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too,
> (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there?
> (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such
> (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate
> (05:57:07) ozizka: which is ugly
> (05:57:14) dmlloyd: I mean arq should
> (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson?
> (05:59:24) ozizka: dmlloyd: It never happened to me actually
> (05:59:49) ozizka: Send me a log if you have one handy
> (06:01:35) dmlloyd: ozizka: no, try running with this command though:
> {code}
> mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \
> -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
> {code}
> (06:13:56) ozizka: dmlloyd: That's on linux?
> (06:14:03) dmlloyd: yes
--
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
14 years, 3 months
[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated AS7-3042:
----------------------------------
Fix Version/s: Open To Community
(was: 7.1.0.Final)
Assignee: (was: Darran Lofthouse)
I am postponing this issue for the moment.
The behaviour of the /console context on port 8080 is supposed to be a simple redirect so that out of the box users that connect to 8080 (Most likely out of habit as that is where previous AS management was performed) can be redirected to the admin console on it's dedicated port.
This re-direct however is not intended to be covering every network topology that can be imagined, once a server is moving beyond the initial set up these welcome pages should be switched off and administrators connect directly to the port hosting the admin console.
For this issue one address has been bound to an IPV6 format of the loopback address and the other address to the IPV4 equivalent - really once an administrator has reached this point they are beyond trying to work out where the admin console is accessible from - also we need to be very careful regarding the information returned from port 8080 as we should not be revealing information about the internal network over this connection as we can not actually verify the remote client has access - this is why the check is limited to verifying the same network interface is being used and relying on a best efforts redirect.
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Fix For: Open To Community
>
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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
14 years, 3 months
[JBoss JIRA] Created: (AS7-783) Deployment scanner service should use a separate operation for each deployment
by Brian Stansberry (JIRA)
Deployment scanner service should use a separate operation for each deployment
------------------------------------------------------------------------------
Key: AS7-783
URL: https://issues.jboss.org/browse/AS7-783
Project: Application Server 7
Issue Type: Task
Components: Console
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
The scanner is creating a single composite op for all deployments encountered in a scan, rather than individual ops. The effect is failures in on deployment results in rolling back the others.
This makes some sense when users change things after startup, since multiple changes within one scan are probably related to each other. But it's not the correct behavior at startup, since multiple apps may not be interrelated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-3336) Values set in OSGi ConfigAdmin do not get written to standalone.xml
by David Bosschaert (JIRA)
David Bosschaert created AS7-3336:
-------------------------------------
Summary: Values set in OSGi ConfigAdmin do not get written to standalone.xml
Key: AS7-3336
URL: https://issues.jboss.org/browse/AS7-3336
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.0.CR1b
Reporter: David Bosschaert
Assignee: Thomas Diesler
When a configuration value gets set in the OSGi Configuration Admin Service this value should get persisted in the configadmin section of standalone.xml.
The ConfigurationAdminTestCase (in as7 testsuite/integration/basic) contains this code:
{noformat} Configuration config = configAdmin.getConfiguration(ConfiguredService.SERVICE_PID);
assertNotNull("Config not null", config);
try
{
Dictionary<String, String> configProps = new Hashtable<String, String>();
configProps.put("foo", "bar");
config.update(configProps);{noformat}
When running this test case with AS7 running I can see that it is run in the server.
I was expecting the foo=bar configuration to appear in the configadmin section of standalone.xml, but it doesn't appear there.
--
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
14 years, 3 months
[JBoss JIRA] (AS7-3334) failed to resolve interface management
by Rafael Soares (JIRA)
[ https://issues.jboss.org/browse/AS7-3334?page=com.atlassian.jira.plugin.s... ]
Rafael Soares deleted AS7-3334:
-------------------------------
> failed to resolve interface management
> --------------------------------------
>
> Key: AS7-3334
> URL: https://issues.jboss.org/browse/AS7-3334
> Project: Application Server 7
> Issue Type: Bug
> Environment: RHEL 6.2
> Open JDK 1.6_20
> Reporter: Rafael Soares
> Assignee: Brian Stansberry
> Labels: domain, scripts
>
> When you try to start a domain using
> ./domain.sh -bmanagement=x.x.x.x
> as described in domain.sh help
> -b <value> JBAS012053: Set system property
> jboss.bind.address to the given value
> -b<interface>=<value> JBAS012054: Set system property
> jboss.bind.address.<interface> to the
> given value
> The domain fails with the following error
> 12:08:29,895 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6
> 12:08:30,183 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 12:08:30,804 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6
> [Host Controller] 12:08:31,705 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA
> [Host Controller] 12:08:31,819 INFO [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.1.0.CR1b "Flux Capacitor" starting
> [Host Controller] 12:08:32,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20]
> [Host Controller] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
> [Host Controller]
> [Host Controller] 12:08:32,934 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014777: Services which failed to start: service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> [Host Controller]
> [Host Controller] 12:08:32,954 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.CR7
> [Host Controller] 12:08:33,871 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.CR7
> [Host Controller] 12:08:34,035 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.CR8
> ^C12:08:56,655 INFO [org.jboss.as.process] (Shutdown thread) JBAS012016: Shutting down process controller
> 12:08:56,664 INFO [org.jboss.as.process.Host Controller.status] (Shutdown thread) JBAS012018: Stopping process 'Host Controller'
> [Host Controller] 12:08:56,703 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.1.0.CR1b "Flux Capacitor" stopped in 43ms
> 12:08:56,753 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 130
> 12:08:56,763 INFO [org.jboss.as.process] (Shutdown thread) JBAS012015: All processes finished; exiting
--
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
14 years, 3 months