June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

Ability to rollback AS version updates -------------------------------------- Key: JBAS-8139 URL: https://jira.jboss.org/browse/JBAS-8139 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> A fixpack installer that handles version rollbacks would be fantastic. >> Of course it needs to remain flexible to work with JBoss installs that >> have been manually modified. Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-4595) Better reporting if a master and slave HC are both launched from the same directory

by Kabir Khan (JIRA)

Kabir Khan created AS7-4595: ------------------------------- Summary: Better reporting if a master and slave HC are both launched from the same directory Key: AS7-4595 URL: https://issues.jboss.org/browse/AS7-4595 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan The only symptom at the moment is hangs on startup on the slave as mentioned in AS7-4593. -- 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 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3974) Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported

by Bela Ban (JIRA)

Bela Ban created AS7-3974: ----------------------------- Summary: Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported Key: AS7-3974 URL: https://issues.jboss.org/browse/AS7-3974 Project: Application Server 7 Issue Type: Feature Request Environment: Linux Fedora 13 Reporter: Bela Ban When starting JBoss like this: "standalone.sh -b 127.0.0.2 -c standalone-ha.xml", the startup fails because 127.0.0.2 cannot be resolved. However, a loopback address should be recognized even if it doesn't resolve to an interface. The code below works for example: {code} InetAddress addr=InetAddress.getByName("127.0.0.5"); boolean is_loopback=addr.isLoopback(); // should be true {code} Loopback addresses are very useful for local testing, ie. starting of multiple JBoss instances on the same box. -- 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 years, 2 months

3
7
0 / 0

[JBoss JIRA] (AS7-4281) Failed to start server when -backup -cached-dc are used together

by Rok Bertoncelj (JIRA)

Rok Bertoncelj created AS7-4281: ----------------------------------- Summary: Failed to start server when -backup -cached-dc are used together Key: AS7-4281 URL: https://issues.jboss.org/browse/AS7-4281 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final, 7.1.2.Final Reporter: Rok Bertoncelj Assignee: Brian Stansberry When starting a slave host controller with *-backup -cached-dc* at the same time, the servers fail to start. Tested with 7.1.1.Final and 7.1.2.Final-SNAPSHOT today. Also tried starting only with -backup first (starts OK) and then for the second time with both options, to make sure that cached configuration is already present if it would help, but it didn't. Host controller should determine availability of domain controller and either backup domain configuration or use the cached one if domain controller is unavailable. {code} 10:35:36,093 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.1.GA 10:35:36,176 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA 10:35:36,225 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" starting 10:35:36,612 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010930: Cannot load the domain model using using --backup 10:35:36,617 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.0.3.GA 10:35:36,631 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.3.GA 10:35:36,649 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.4.GA 10:35:36,970 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010907: Failed to start server (server-one): java.util.NoSuchElementException: No child 'server-group' exists at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:298) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ModelNode.require(ModelNode.java:812) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.host.controller.ModelCombiner.<init>(ModelCombiner.java:139) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.createManagedServer(ServerInventoryImpl.java:474) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:160) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:150) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:521) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler.cleanStartServers(StartServersHandler.java:114) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler.access$300(StartServersHandler.java:50) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler$1.execute(StartServersHandler.java:94) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.executeDirect(PrepareStepHandler.java:122) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:74) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService.startServers(DomainModelControllerService.java:443) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:403) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] 10:35:36,989 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:29999 10:35:37,015 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010907: Failed to start server (server-two): java.util.NoSuchElementException: No child 'server-group' exists at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:298) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ModelNode.require(ModelNode.java:812) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.host.controller.ModelCombiner.<init>(ModelCombiner.java:139) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.createManagedServer(ServerInventoryImpl.java:474) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:160) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:150) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:521) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler.cleanStartServers(StartServersHandler.java:114) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler.access$300(StartServersHandler.java:50) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.StartServersHandler$1.execute(StartServersHandler.java:94) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.executeDirect(PrepareStepHandler.java:122) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:74) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService.startServers(DomainModelControllerService.java:443) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:403) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] 10:35:37,082 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" (Host Controller) started in 1249ms - Started 11 of 11 services (0 services are passive or on-demand) {code} -- 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 years, 2 months

4
5
0 / 0

[JBoss JIRA] (AS7-4555) Resolve startup dependency between master hostController and slave hostControllers.

by karin k (JIRA)

karin k created AS7-4555: ---------------------------- Summary: Resolve startup dependency between master hostController and slave hostControllers. Key: AS7-4555 URL: https://issues.jboss.org/browse/AS7-4555 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.1.Final Reporter: karin k Assignee: Brian Stansberry #Current situation:* *The slave hostController can be started using option --cached-dc Result: the slave hostContoller will be started given that a local copy of the domain.xml (exact name domain.cached-remote.xml ) is available (created by a startup using -backup and an available master hostController) The slave hostController will never register itself towards the master domain hostController (regardless of whether the master domain controller is running during startup or will be started afterwards) *The slave hostController can be started without any option If the master hostController is not running during startup of the slave, the startup of the slave will fail. *The slave hostController can be started with option -backup If the master hostController is not running during startup of the slave, the startup of the slave will fail. If the master hostController is running, the slave will store a copy of the domain.xml locally. A successful startup of the whole domain is only possible when the hostControllers are started in the correct sequence (master hostController must be available when slave host Controllers are trying to register). From my point of view a successful startup means that all hostControllers can start successfully and additionally it is possible to manage the slave hostController by means of the master hostController. #Requirement To let a JBoss domain act and started in the correct way (meaning central management is possible) the following should be fullfilled *If the master hostController is not running, the slave should still be able to start and work with its local copy of the domain.xml *If the master hostController is started after the slave hostController, the slave host controller should still be able to start successfully but should in parallel recognize when the master hostController is finally available and register itself *There should be the possiblity to store a local copy of the domain master hostController in parallel with the approach of starting up when the master hostController is not running (in this case the master domain.xml cannot be stored locally but anyway startup is possible). (see also https://issues.jboss.org/browse/AS7-4281) Regards Karin -- 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 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-5007) process-controller command line parses usage arg at wrong place

by Bernd Eckenfels (JIRA)

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8842) Security checks when recursively reading resources

by Emanuel Muckenhuber (JIRA)

Security checks when recursively reading resources -------------------------------------------------- Key: JBAS-8842 URL: https://issues.jboss.org/browse/JBAS-8842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Emanuel Muckenhuber Assignee: Darran Lofthouse Currently the "read-resource" operation (GlobalOperationHandlers.ReadResourceHandler) just clones the subModel when recursively reading resources. We need to make sure that to also check the permissions for the children a node contains. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
7
0 / 0

[JBoss JIRA] (AS7-4701) One time password for management interfaces

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4701: ------------------------------------- Summary: One time password for management interfaces Key: AS7-4701 URL: https://issues.jboss.org/browse/AS7-4701 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 This task is to look into one time password use for the management consoles. This needs some further investigation as there is a trade off between ensuring a password is really one time and not valid for replays after use yet allowing a users web browser to keep establishing connections without forcing a new authentication every few minutes. The native interface also needs similar consideration however the native interface does allow for connections to be kept open for a long time more naturally. -- 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 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-4039) Pushing configuration artifacts to domain servers

by Darragh Sherwin (JIRA)

Darragh Sherwin created AS7-4039: ------------------------------------ Summary: Pushing configuration artifacts to domain servers Key: AS7-4039 URL: https://issues.jboss.org/browse/AS7-4039 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Darragh Sherwin Assignee: Brian Stansberry It should be possible to push configurations artifacts like property files, keystores, etc to domain servers from a domain controller and for applications to reference these configuration artifacts in a generic manner. Weblogic provides this functionality -- 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 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3568) Increase Test Coverage of Domain Management Security Options

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3568: ------------------------------------- Summary: Increase Test Coverage of Domain Management Security Options Key: AS7-3568 URL: https://issues.jboss.org/browse/AS7-3568 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.1.Final Presently there is plenty of testing relating to the default security options but now we need coverage of the non default options especially SSL. -- 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 years, 2 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2012