[
https://issues.apache.org/jira/browse/ARIES-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180731#comment-16180731
]
Grzegorz Grzybek commented on ARIES-1174:
-----------------------------------------
I see this problem in yet another scenario. I have two bundles:
* a blueprint bundle declaring <bean> and <service> for
{{org.apache.camel.spi.IdempotentRepository}} implementation
* a blueprint bundle with Camel context using file endpoint with
{{idempotentRepository=#messageIdRepository}} reference.
When I first stop Camel context bundle and then one with
{{IdempotentRepository}} service, everything's fine, but changing the order
leads to unnecessary wait. Camel wants to stop and it waits for the repository.
It's not that trivial as it seems at first glance - there may be cases where
target OSGi service *is needed* during shutdown of blueprint bundle using
<reference>, it could be ignored, but it (IMO) has to be explicit decision.
> Avoid service reference timeout when system bundle is stopping
> --------------------------------------------------------------
>
> Key: ARIES-1174
> URL: https://issues.apache.org/jira/browse/ARIES-1174
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: blueprint-core-1.1.0
> Reporter: Benno Geißelmann
> Assignee: Grzegorz Grzybek
>
> The default timeout of Blueprint to wait for a service to come is 5 minutes.
> A problem which comes with the timeout behaviour is, that in some states you
> don't want to wait for the service. For example if the system bundle is in
> state "stopping" this timeout will cause that the stopping takes 5 minutes.
> In my opinion this makes no sense as the container will shutdown so there
> shouldn't be waited for a service to come.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
