Hi Ioannis, I am sorry I have not had a chance to look at your use-case. I will look at it in the next day or two.
In the meantime, Can you go ahead and add a Jira issue against this Cheers, Ashwin -------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FuseSource (a Progress Software Corporation subsidiary) http://www.fusesource.com <http://www.fusesource.com/> Mobile: (972)-971-1700 Blog:http://opensourceknowledge.blogspot.com <http://opensourceknowedge.blogspot.com/> --------------------------------------------------------- From: Ioannis Canellos <[email protected]> Date: Fri, 20 May 2011 15:53:29 +0300 To: <[email protected]>, Ashwin Karpe <[email protected]> Subject: Re: Camel 2.7.1 graceful termination. I am attaching a project that reproduces the issue. The project is be deployed as a bundle on karaf (will also require an activemq broker) or servicemix and contains two simple routes: Route 1: Consumes messages from an activemq queue and load balances the messages between two log endpoints. Route 2: Consumes messages from an activemq queue and load balances the messages between two activemq producer endpoints. This route uses XA transactions. Instructions on how to reproduce it. Once the bundle is started you can add a couple of messages to "message.outbound" queue, wait till they are all consumed and then stop the bundle. You will notice that a consumer will stay alive on that queue even if the bundle is stopped. The same will happen if you add messages to the second route. Please note that both routes will work perfect if they are on their own. I think that this is a bug. wdyt? Should I open a Jira? -- Ioannis Canellos http://iocanel.blogspot.com <http://iocanel.blogspot.com/> Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer
