Hi You can use JMX to start/stop CamelContext. We have it on the roadmap for Camel 2.x to let Camel be much more dynamic manageable at runtime to add/remove/pause producers/consumers etc. But stopping and starting a CamelContext should be doable.
The Main in camel-spring is usually for running Camel during development or testing using camel:run or running Camel standalone. At production Camel is usually embedded in some sort of container: - AMQ - SMX - Tomcat - OSGi - J2EE - etc. On Fri, Jan 16, 2009 at 9:13 AM, harinair <har...@hotmail.com> wrote: > > So that the Camel router is shutdown for the maintenance or upgrade. There is > no need to shutdown your broker with Camel. Right? For my case my broker > services many other applications including the Camel based message router. I > can independently stop each other but if I stop Message Broker then Camel > logs shows Exceptions... hence in that case I may stop the Camel first and > then the Broker. > > Probably you have this question since you run Camel within the Apache > ActiveMQ broker? > > Hari Gangadharan > > > selezovikj wrote: >> >> In the doStop() method of org.apache.camel.spring.Main class the >> application context is closed. >> What will this actually do ? >> Let us say in my camel-server.xml file, I have definitions for an activemq >> broker running on port 61616. >> When I close the application context the broker does not shutdown. >> What does closing the application context result with ? >> >> > > -- > View this message in context: > http://www.nabble.com/Two-questions%3A-Stopping-Camel-and-intercept-before-retry-tp21323127s22882p21494364.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- ------- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
