[ 
https://issues.apache.org/jira/browse/ARIES-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624363#comment-14624363
 ] 

metatech commented on ARIES-805:
--------------------------------

[~gnt] Thanks Guillaume for looking into this.
However, I discovered in between that this change would also require a change 
in the Javadoc of class BlueprintEvent, which mentions : 
"Must be a non-empty array for event types GRACE_PERIOD and WAITING".
I do know whether this comment is specific to the Aries Blueprint 
implementation or applicable for all Blueprint implementations.

> 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)

Reply via email to