You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2012/08/20 23:01:39 UTC

[jira] [Resolved] (ARIES-907) Persisted, unscoped subsystems are not being correctly started on restarts.

     [ https://issues.apache.org/jira/browse/ARIES-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Ross resolved ARIES-907.
-----------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1375215.
                
> Persisted, unscoped subsystems are not being correctly started on restarts.
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-907
>                 URL: https://issues.apache.org/jira/browse/ARIES-907
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: John Ross
>            Assignee: John Ross
>
> Basically, a subsystem should always be started when requested except on a restart (e.g., subsystems implementation bundle or framework) if the subsystem is not ready. The term "ready" is defined as at least one parent is in the STARTING or ACTIVE state and autostart is set to started. Autostart is set to started whenever an explicit start operation is requested (i.e. the start method of that subsystem is directly invoked by a client). It is also automatically set to started if the subsystem is content of another subsystem. Autostart is set to stopped whenever an explicit stop operation is requested (i.e. the stop method of that subsystem is directly invoked by a client).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira