Hi all, I encountered this in an application I am working on, and it can be reproduced in a simple application: http://pastebin.com/VZHWKDRG
The scenario: start ActiveMQ, start the simple app. Then shutdown ActiveMQ (ctrl+c in the window). Now the Camel application shuts down as well (logging output here: http://pastebin.com/L4rnKv19 ). Somehow, somewhere a JVM shutdown is initiated by this scenario. But I can't find out why/where. As an experiment I added a JVM shutdownhook and put a breakpoint on it. This prevented the application from shutting down. Now bring up ActiveMQ again (while the breakpoint is still active and hence the simple app is still running), and I saw the JmsMessageListenerContainer happily resuming the connection to ActiveMQ again! This is the behavior I expected and that I would like to have. Can anyone shed some light as to what is going on here? Thanks, Sander
