On Wed, Aug 29, 2012 at 5:12 PM, towe <tobias.westerb...@cubeia.com> wrote: > I think you are on to something here! :-) > > One major difference I spotted between your test and mine is the standalone > broker. > > When I run my own test against an external broker everything works as > expected, the message is still there after camel shutdown! > > But when I run with an embedded broker started by Spring the message is > gone. > > Maybe the shutdown (order) of camel and the broker when the spring context > is destroyed has anything to do with it... >
Yeah good point, you can use the depends-on attribute in the Spring XML file, to tell it to have the broker depend on <camelContext>. This is needed to have spring shutdown camel first. > > > Claus Ibsen-2 wrote >> >> I created an unit test trying to reproduce an issue >> http://svn.apache.org/viewvc?rev=1378526&view=rev >> >> It works for me. I start up a remote AMQ broker first. In this case >> Apache ActiveMQ 5.6.0. >> Running the test ensures the message is rolled back, and using the AMQ >> web console I can see the message starts on the queue. >> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/shutting-down-Camel-in-flight-messages-gone-tp5717930p5718272.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
