You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Zoran Regvart (JIRA)" <ji...@apache.org> on 2017/05/11 08:00:16 UTC

[jira] [Created] (CAMEL-11261) Revise Camel context destruction in Spring (Boot) applications

Zoran Regvart created CAMEL-11261:
-------------------------------------

             Summary: Revise Camel context destruction in Spring (Boot) applications
                 Key: CAMEL-11261
                 URL: https://issues.apache.org/jira/browse/CAMEL-11261
             Project: Camel
          Issue Type: New Feature
          Components: camel-spring, camel-spring-boot
            Reporter: Zoran Regvart
            Assignee: Zoran Regvart
            Priority: Minor


There have been issues in the past where the user needs to control the destruction order of CamelContext with regards to other dependencies. Notably resources such as connection pools. AMQ-3988 notes one of those for JMS connection pools.
Prompted by the [discussion|http://camel.465427.n5.nabble.com/OnApplicationEvent-not-called-with-CamelAutoConfiguration-tp5798802.html] on the user forum we should investigate if there is a way we can get CamelContext priority on shutdown.
One idea is to use lifecycle beans as in [PR#1685|https://github.com/apache/camel/pull/1685].
We should evaluate if this change introduces other issues.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)