Hi Try removing your <onException> which has that mark rollback only.
Spring JMS is a bit weird when it comes to marking a TX as rollback. It tends to prefer a runtime exception being thrown over marking the TX explicit as rollback only. On Mon, Aug 27, 2012 at 10:12 AM, towe <tobias.westerb...@cubeia.com> wrote: > Hello, > > They don't end up in the DLQ in this case. :-( > > If I set maximumRedeliveries on the error handler to 5, for example, the > messages will end up in the DLQ. But in my case I have maximum deliveries > set to -1 (unlimited) and the timeout of the DefaultShutdownStrategy set to > 5 seconds. > > When stopping the application by ctrl+c the message is completely gone after > the 5s timeout. > > The only workaround so far is to set the timeout to -1. That will force the > shutdown to keep trying forever. The application now needs to be killed the > hard way, but at least the message is not lost. Unfortunately this means > that hot-redeploy in an application server won't work. > > /tw > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/shutting-down-Camel-in-flight-messages-gone-tp5717930p5718112.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
