I am trying to set up a camel route that forwards jms messages from one persistent (local) queue to another remote jms queue.
If the remote connection is down the incoming message should be left on the in-queue. I managed to get this to work using transactions. But the problem I have now is that doing a graceful shutdown removes the in-flight messages (after timing out on the DefaultShutdownStrategy). Killing the Camel process the hard way (kill -9) preserves the messages on the queue, which is what I want. To summarize, what I want is: 1. forward from queue A to queue B 2. rollback A (leave in queue) if B is down 3. repeat trying forever 4. to be able to shutdown camel without dropping in-flight messages /tw -- View this message in context: http://camel.465427.n5.nabble.com/shutting-down-Camel-in-flight-messages-gone-tp5717930.html Sent from the Camel - Users mailing list archive at Nabble.com.
