If you enable TRACE logging on org.apache.camel.component.jms.EndpointMessageListener
Then the onMessage method (which is invoked when a msg is consumed) has TRACE logging. Can you see if you get a begin + end logs for each message. It may be that the broker does not get any rollback commands for the message when Camel is forcing shutdown. Which means the broker may think the message is inflight. It ought however to know the message is no longer in-flight, when the consumer is no longer active. Anyway the TRACE logging may help a bit to see what goes on. There is On Mon, Aug 27, 2012 at 10:32 AM, towe <tobias.westerb...@cubeia.com> wrote: > Hi, > > Nope, didn't make a difference. Exactly the same behaviour as before. > > /tw > > > Claus Ibsen-2 wrote >> >> 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. >> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/shutting-down-Camel-in-flight-messages-gone-tp5717930p5718117.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
