Dears,
I think I found the culprit.
I did not mentioned that in the same application,we are using also
Spring-Batch runtime (through JSR API). The Spring context of the
Spring-Batch is inheriting of a common shared context to allow the usage of
some bean in the jobs definition. But since we are using Camel (part of
share context), when a job is starts it seems to try to start again Camel
(not really a problem) but when it stops it seems ti unload its own context
and raise an 'ContextClosedEvent' event that is processed by the
CamelContext class and shutdown Camel. From this moment Camel is available
during the run of Jobs!
If somebody has this kind of configuration and it does have this kind of
issue. I am interested in their configuration. Not directly an Camel issue.
But in there is a way that Came can to filter some event base on their
source it could help.
The event looks like :
/2016-03-09 10:42:16,210|.kernel.Default (self-tuning)'|
| | | INFO
[org.springframework.batch.core.jsr.configuration.xml.JsrXmlApplicationContext:960]
Closing
org.springframework.batch.core.jsr.configuration.xml.JsrXmlApplicationContext@413a14cc:
startup date [Wed Mar 09 10:42:15 CET 2016]; parent: ApplicationContext
'baseContext'
2016-03-09 10:42:16,210|.kernel.Default (self-tuning)'|
| | |DEBUG [org.apache.camel.spring.SpringCamelContext:130]
onApplicationEvent:
*org.springframework.context.event.ContextClosedEvent[source=org.springframework.batch.core.jsr.configuration.xml.JsrXmlApplicationContext@413a14cc:
startup date [Wed Mar 09 10:42:15 CET 2016]; parent: ApplicationContext
'baseContext'] *
2016-03-09 10:42:16,211|.kernel.Default (self-tuning)'|
| | | INFO [org.apache.camel.spring.SpringCamelContext:3023]
Apache Camel 2.16.2 (CamelContext: sep-eval-camel-service) is shutting down
/
Tx,
Cataldo
--
View this message in context:
http://camel.465427.n5.nabble.com/Unexpected-shutdow-of-the-Camel-context-tp5778699p5778770.html
Sent from the Camel - Users mailing list archive at Nabble.com.
