[
https://issues.apache.org/jira/browse/ARIES-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180460#comment-16180460
]
Grzegorz Grzybek commented on ARIES-1256:
-----------------------------------------
You're mixing reference timeout (which works) with entire blueprint timeout.
When BlueprintContainer is run, it first sets default (entire) blueprint
timeout to 5 minutes, and then parses manifest entry for Bundle-SymbolicName.
If there's:
{noformat}
Bundle-SymbolicName: my.blueprint.bundle;blueprint.timeout=120000
{noformat}
Then you'll get the expected behavior. At entire blueprint container level you
(aries) don't know which of the <reference>s will timeout. So when designing BP
application, please select blueprint.timeout as maximum of each of the
reference timeouts.
> Individual reference timeout is ignored
> ---------------------------------------
>
> Key: ARIES-1256
> URL: https://issues.apache.org/jira/browse/ARIES-1256
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: blueprint-core-1.1.0
> Reporter: Irina Boldea
>
> Explicitly setting the timeout for an individual reference is ignored and the
> the default one of 5 minutes is taken.
> {code}
> <reference id="exampleRef" interface="org.example.ExampleRef"
> timeout="120000"/>
> {code}
> The TimeoutException is thrown only after 5 minutes instead of 2 minutes.
> {code}
> Unable to start blueprint container for bundle org.example.testbundle due to
> unresolved dependencies [(objectClass=org.example.ExampleRef)]
> java.util.concurrent.TimeoutException
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:375)
> {code}.
> Thank you.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
