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

Thu Apr 19 02:55:17 EDT 2012

     [ https://issues.jboss.org/browse/AS7-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

karin k updated AS7-4555:
-------------------------

        Description: 
*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

  was:
#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

    Forum Reference: https://community.jboss.org/message/730624#  (was: https://community.jboss.org/message/730624#)

> 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