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

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Implemented
• Fix Version/s: 2.20.0
• Component/s: camel-spring, camel-spring-boot
• Estimated Complexity: Unknown
• Assignee: Zoran Regvart
• Reporter: Zoran Regvart
• Created: 11/May/17 07:59
• Updated: 29/Aug/17 10:21
• Resolved: 13/Jun/17 13:12

Description

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 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.
We should evaluate if this change introduces other issues.

Issue Links

• is related to: CAMEL-11715 Camel Spring : unable to mix xml and java routes
• is related to: CAMEL-9431 camel-spring-boot - TypeConverter autoconfiguration leads to invalid shutdown sequence
• is related to: CAMEL-9830 camel-spring-javaconfig - Add routes like spring-boot does
• relates to: CAMEL-11405 Create a per-SpringCamelContext replacement for `noStart` flag
• links to: GitHub Pull Request #1685
• links to: Issue reported by wildfly-camel team