[CAMEL-9431] camel-spring-boot - TypeConverter autoconfiguration leads to invalid shutdown sequence

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.16.1
• Fix Version/s: 2.16.3, 2.17.0
• Component/s: camel-spring-boot
• Assignee: Claus Ibsen
• Reporter: Laurent Chiarello
• Created: 17/Dec/15 14:12
• Updated: 19/May/17 09:20
• Resolved: 10/Feb/16 14:04

Description

When using autoconfiguration provided by the camel-spring-boot artifact, a TypeConverter bean is automatically registered into the Spring context:

TypeConversionConfiguration.java

@Bean
TypeConverter typeConverter(CamelContext camelContext) {
    return camelContext.getTypeConverter();
}

The returned bean is an instance of DefaultTypeConverter, which in turn implements ServiceSupport and its method public void shutdown(). This method is infered as a destroy-method by Spring, and called during the shutdown of the ApplicationContext.

As a consequence, the TypeConverter will be destroyed before the CamelContext, effectively preventing any type conversion support for the inflight messages that have still to be processed during the graceful shutdown period of Camel.

AFAIK the simple fix would be to disable the destroy-method inference using @Bean(destroyMethod=""). This will let Camel have a chance to perform a clean shutdown in the right sequence.

As a workaround, it is possible to entirely disable the registration of the type converter in Spring using the property
camel.springboot.type-conversion = false

Issue Links

• relates to: CAMEL-11008 Consumer/Producer templates are not stopped when auto-configured in Spring Boot
• relates to: CAMEL-11261 Revise Camel context destruction in Spring (Boot) applications