aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] [Updated] (ARIES-1430) Blueprint bundle shut down after timeout even if all dependencies are present at that time
Date Sun, 11 Oct 2015 19:06:05 GMT


Christian Schneider updated ARIES-1430:
    Priority: Critical  (was: Major)

> Blueprint bundle shut down after timeout even if all dependencies are present at that
> ------------------------------------------------------------------------------------------
>                 Key: ARIES-1430
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.4.4
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Critical
>             Fix For: blueprint-core-1.4.5
> When I run the jpa blueprint example it works fine at the start but after 4 minutes I
see the exception below.
> When the blueprint context is created the future for the timeout of dependencies is canceled.
> In Aries JPA I use a ComponentDefinitionRegistryProcessor to scan for the @PersistenceContext
annoations and register a service reference for these. I think that this triggers
> the future for the timeout of such dependencies again. If this processor is called after
the future is canceled above then the future will not be canceled anymore. So after the timeout
(5min) it will
> trigger and stop the blueprintcontainer even if all dependencies are satisfied now.
> This is the code that is executed after the timeout:
> It matches the exception and explains why there are no unresolved dependencies.
> I would be happy about feedback from anyone with deeper blueprint knowledge. Is what
I do there in Aries JPA incorrect? If yes then we need a new Aries JPA release .. though I
am not sure how to better address the problem.
> If it is correct then we need to fix this in blueprint core.
> A simple fix/workaround would be to check if there are no unresolved dependencies when
the future times out and not stop the container in this case. A better fix would cancel the
future as soon as all dependencies are fulfilled.
> 2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 | BlueprintContainerImpl         
 | 12 - org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint container for
bundle due to unresolved dependencies
> java.util.concurrent.TimeoutException
>     at org.apache.aries.blueprint.container.BlueprintContainerImpl$[12:org.apache.aries.blueprint.core:1.4.4]
>     at[12:org.apache.aries.blueprint.core:1.4.4]
>     at java.util.concurrent.Executors$[:1.8.0_60]
>     at[:1.8.0_60]
>     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201([:1.8.0_60]
>     at java.util.concurrent.ScheduledThreadPoolExecutor$[:1.8.0_60]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker([:1.8.0_60]
>     at java.util.concurrent.ThreadPoolExecutor$[:1.8.0_60]
>     at[:1.8.0_60] 

This message was sent by Atlassian JIRA

View raw message