Dears, I have a strange issue. I have an JEE application (ear) that I deployed on a Frontend servers (2) and Backend servers (2). The same ear is deployed on all servers and a property file is used to activate or not the components and or camel routes on particular servers. I am using Camel version 2.16.2 Spring 4.2.4 and defined the routes in Spring XML (Spring-camel):
1) route reading from direct endpoint to send a jpa endpoint to persit the message. this message will be read by route 2) (jpa endpoint) 2) route reading from a jpa endpoint to read message to process by enriching the message that will be sent to route 3) (direct endpoint) 3) route reading from a direct enpoint (feeded by route 2) to aggragate the message and sending the aggegated message to a bean endpoint. I ordered the startup of the routes to be sure that their are always reachable. On all server the Camel context is configured with autostatup to true in the Spring XML context. On the Frontend servers only route 1 is activated. On backend servers all the three routes are activated. Logically everything seems OK for me. But after a while (couples of days at least 4 or 5) the we observer in the log the the context is shuting down and there for the only route activate becomes unusable. What can triggers the context to be shutdown? I joinded the full configuration and I hope someone can point what parameter is wrong or missing. Is this link to a default shutdow startegy? CamelContext.xml <http://camel.465427.n5.nabble.com/file/n5778699/CamelContext.xml> Thanks in advance, Cataldo. -- View this message in context: http://camel.465427.n5.nabble.com/Unexpected-shutdow-of-the-Camel-context-tp5778699.html Sent from the Camel - Users mailing list archive at Nabble.com.
