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 Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer *
camel-restarts-use-case.tar.gz
Description: GNU Zip compressed data
