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

Mark Nuttall commented on ARIES-323:
------------------------------------

We now log these events. For example bringing Aries up one sees, 

[25/01/11 10:25:57:035 GMT] 00000019 BlueprintCont I 
org.apache.aries.blueprint.container.BlueprintContainerImpl doRun Bundle 
org.apache.aries.application.deployment.management is waiting for dependencies 
[(objectClass=org.apache.aries.application.modelling.ModelledResourceManager), 
(objectClass=org.apache.aries.application.management.spi.runtime.LocalPlatform),
 (objectClass=org.apache.aries.application.modelling.utils.ModellingHelper), 
(objectClass=org.apache.aries.application.management.spi.resolve.PostResolveTransformer),
 (objectClass=org.apache.aries.application.modelling.ModellingManager), 
(objectClass=org.apache.aries.application.management.spi.resolve.AriesApplicationResolver)]
[25/01/11 10:25:57:055 GMT] 00000019 BlueprintCont I 
org.apache.aries.blueprint.container.BlueprintContainerImpl doRun Bundle 
org.apache.aries.application.management is waiting for dependencies 
[(objectClass=org.apache.aries.application.management.spi.resolve.DeploymentManifestManager),
 
(objectClass=org.apache.aries.application.management.spi.runtime.LocalPlatform),
 (objectClass=org.apache.aries.application.DeploymentMetadataFactory), 
(objectClass=org.apache.aries.application.management.spi.runtime.AriesApplicationContextManager)]

Please close this JIRA if the current behaviour is sufficient. 

> Emit an event/warning when a blueprint cannot find its services and moves 
> into the wait state
> ---------------------------------------------------------------------------------------------
>
>                 Key: ARIES-323
>                 URL: https://issues.apache.org/jira/browse/ARIES-323
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: 0.1
>            Reporter: Alasdair Nottingham
>
> If a mandatory dependency is not available the bundle goes into a wait state 
> waiting up to n minutes (where n is 5 by default) for the dependencies to 
> become available. This means if a mistake is made the user has to wait 5 
> minutes to get any indication of a problem. It would be really good if we 
> could emit an event, somehow, that indicated that the bundle was in this wait 
> state when entered to reduce this time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to