You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/07/02 15:43:00 UTC

[jira] [Commented] (ARIES-1174) Avoid service reference timeout when system bundle is stopping

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

Guillaume Nodet commented on ARIES-1174:
----------------------------------------

bq. I think the solution would be to use the new {{ext:lifecycle="static"}} ({{ext}} 1.6 namespace) on the {{reference}} element.  This should destroy the {{CamelContext}} when the reference isn't satisfied anymore.

> 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: Guillaume Nodet
>            Priority: Major
>
> 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
(v7.6.3#76005)