On Mon, Jul 11, 2011 at 2:28 PM, Claus Ibsen <[email protected]> wrote: > How do you shutdown the AMQ broker?
I ctrl-c in the broker console. > And why do you want to shutdown the broker, but keep on running Camel? Just to make it clear: the Camel app is running standalone here, not inside the broker. The camel route is triggered by incoming messages on a queue. If the queue cannot be read, I want my app to keep trying until it can read from the queue again (meanwhile logging the errors it encounters ofcourse). Doesn't seem like an uncommon requirement to me. Also, this is the standard behavior of the DefaultMessageListenerContainer that powers the JmsListener. However, the spurious shutdown of the JVM in this scenario prevents this mechanism from kicking in (more precisely: I see *some* reconnect attempts, but the shutdown procedure kicks in anyway). The whole point of using JMS to me is the decoupling of producer/consumer. However as it stands, my app cannot survive a broker unavailability event? Thanks, Sander
