I ran into the following problem when using autoconfiguration provided by
/camel-spring-boot/ artifact. By default, there is a configuration classes
that automatically registers a /TypeConverter/ bean into the Spring context:


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.

I have attached a JUnit test case to illustrate this behavior. AFAIK the
simple fix would be to disable the destroy-method inference:
/@Bean(destroyMethod="")/. As a workaround I had to disable type conversion
support using the property 

CamelSpringBootShutdownTest.java
<http://camel.465427.n5.nabble.com/file/n5775220/CamelSpringBootShutdownTest.java>
  

Lch



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-SpringBoot-integration-Invalid-shutdown-sequence-tp5775220.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to