[
https://issues.apache.org/jira/browse/CAMEL-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006734#comment-17006734
]
Luigi De Masi commented on CAMEL-14332:
---------------------------------------
What is happening is that when the blueprint timeout is triggered, the
ShutdownStrategy is forced to shutdown earlier than its deadline so user
defined or default timeout is not effective when it's longer than one minute.
> camel-blueprint - Camel route does not consider the value of ShutdownStrategy
> timeout.
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-14332
> URL: https://issues.apache.org/jira/browse/CAMEL-14332
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
> Affects Versions: 2.24.2, 3.0.0
> Reporter: Luigi De Masi
> Assignee: Luigi De Masi
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In an OSGI context when Blueprint framework is used, if the shutdown strategy
> timeout is greater than one minute, the timeout is not effective.
> When the bundle is stopping, this is the call chain:
> {noformat}
> BlueprintEventDispatcher (timeout 1 minute) -->
> BlueprintCamelContext.blueprintEvent --> BlueprintCamelContext.stop (timeout
> 5 minute by default){noformat}
> So when the Shutdown strategy timeout is longer than one minute, the
> [BlueprintEventDispatcher timeout
> |https://github.com/apache/aries/blob/ee16fd21f22624947a991c80503d819424497567/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintEventDispatcher.java#L188-L193]is
> triggered for first, making the shutdown strategy useless.
> The solution to this, is to remove the piece of code that handle the destroy
> event from
> [BlueprintCamelContext|https://github.com/apache/camel/blob/568f9a1e0b0e8765bb4ff8a0f82b83dd85eeae24/components/camel-blueprint/src/main/java/org/apache/camel/blueprint/BlueprintCamelContext.java#L187-L194].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
