Hi, It is quite straightforward. When the ActiveMQ broker is down a connection cannot be created to the broker. If one already exists, the connection becomes stale and unusable due to non-availability of the broker. This would cause in your case an exception to be thrown. Since the exception is not trapped in any way, the code is not running in a container but on the Java mainline, the JVM is destroyed following the stack trace.
If on the other hand, you add an exception handler to the camel route, you will find that the exception can be caught and handled without destroying the JVM. Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com CamelOne 2011: http://fusesource.com/camel2011 --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Broker-shutdown-also-shuts-Camel-application-down-tp4549804p4551079.html Sent from the Camel - Users mailing list archive at Nabble.com.
