You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Ioannis Canellos <io...@gmail.com> on 2011/05/18 16:45:13 UTC

Camel 2.7.1 graceful termination.

Hi,

I am using Camel 2.7.1 with Karaf 2.2.0 and I am experiencing a weird
behavior. When I restart the bundles that contain my routes *(declared using
camel-spring not camel-blueprint) *I see that* the routes do not stop
gracefully.

*What do I mean by not gracefully? I use camel-jms to consume messages. When
I stop my bundle I still see the old consumers being active to the queue.
When I restart* my bundle I see double the number of consumers.

This is a behavior I don't remember having with camel 2.5.0 which was the
version I used before upgrading to 2.7.1.

Do I miss some new configuration option introduced after 2.5.0? Is it a bug?

*Thanks in advance,

*Ioannis Canellos*
*
 http://iocanel.blogspot.com

Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache ServiceMix <http://servicemix.apache.org/>  Committer
*

Re: Camel 2.7.1 graceful termination.

Posted by Ashwin Karpe <ak...@fusesource.com>.
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 <io...@gmail.com>
Date:  Fri, 20 May 2011 15:53:29 +0300
To:  <us...@camel.apache.org>, Ashwin Karpe <ak...@fusesource.com>
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




Re: Camel 2.7.1 graceful termination.

Posted by Ioannis Canellos <io...@gmail.com>.
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
*

Re: Camel 2.7.1 graceful termination.

Posted by Ioannis Canellos <io...@gmail.com>.
Hi Ashwin,

thanks for the quick response. This is indeed a strange behavior. I will try
to create a use-case that reproduces the problem and let you know.

 --
*Ioannis Canellos*
*
 http://iocanel.blogspot.com

Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache ServiceMix <http://servicemix.apache.org/>  Committer
*

Re: Camel 2.7.1 graceful termination.

Posted by Ashwin Karpe <ak...@fusesource.com>.
Hi,

This is quite unusual. I have never run into it before. Do you have a simple
example use-case that I could use to check this out...

Cheers,

Ashwin...

-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com 

Blog: http://opensourceknowledge.blogspot.com 
CamelOne 2011: http://fusesource.com/camel2011 
---------------------------------------------------------
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-2-7-1-graceful-termination-tp4406666p4407838.html
Sent from the Camel - Users mailing list archive at Nabble.com.