You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2015/07/13 10:34:05 UTC

[jira] [Updated] (ARIES-805) Blueprint container should re-enter Creating state when GracePeriod state is finished

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

Guillaume Nodet updated ARIES-805:
----------------------------------
    Fix Version/s:     (was: blueprint-core-1.4.4)
          Summary: Blueprint container should re-enter Creating state when GracePeriod state is finished  (was: Send an empty GRACE_PERIOD event at the end of the grace period to notify listeners)

Unfortunately, the BlueprintEvent does not allow sending a GRACE_PERIOD event with no missing dependencies :-(

> Blueprint container should re-enter Creating state when GracePeriod state is finished
> -------------------------------------------------------------------------------------
>
>                 Key: ARIES-805
>                 URL: https://issues.apache.org/jira/browse/ARIES-805
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: 0.2
>         Environment: ServiceMix 4.3
>            Reporter: metatech
>            Priority: Minor
>         Attachments: ExitGracePeriodNotifier.java
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When a component is starting, the Blueprint container implementation (class BlueprintContainerImpl) enters the "Creating" state.
> If a external dependency (namespace handler or OSGI service reference) is not available yet, it enters the "GracePeriod" state.
> Once the GracePeriod is finished, the creation is performed, which ends up with the "Created" state.
> However, when the creation takes a long time (for instance, in an ActiveMQ cluster configuration, the slave node waits forever until the master node goes down), the state is reported as "GracePeriod", although it is actually suspended in the "Creating" state.
> This reporting can be misleading and makes troubleshooting require detailed understanding of the Blueprint states and transitions semantics .  It would be clearer to re-fire a "Creating" state Blueprint event (possibly with the "replay" flag).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)