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