You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by yogu13 <yo...@gmail.com> on 2015/06/05 06:09:51 UTC
Camel Graceful Shutdown Issue for JMS endpoints
Hello,
I am using camel 2.14.1 in karaf with ActiveMQ 5.10. During shutdown process
once the embedded broker is stopped, I see that graceful shutdown for routes
having jms endpoints are taking a very long time as the endpoint are busy
refreshing the JMS connections instead of shutting down(note: there are no
inflight messages for processing at that point in time) and finally after a
timeout allow the route to be destroyed and the shutdown process to proceed.
JDK version being used is 1.7.x
Not sure why this keeps refreshing the JMS connections instead of shutdown.
I see that the spring provided message listener containers are used which
could fail to interpret a shutdown.
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Graceful-Shutdown-Issue-for-JMS-endpoints-tp5767883.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Graceful Shutdown Issue for JMS endpoints
Posted by yogu13 <yo...@gmail.com>.
Anyone ?
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Graceful-Shutdown-Issue-for-JMS-endpoints-tp5767883p5767909.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Graceful Shutdown Issue for JMS endpoints
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
If you have setup connection pool then make sure to setup its init and
destroy methods so the pool is shutdown cleanly as well
http://camel.apache.org/activemq
On Fri, Jun 5, 2015 at 6:09 AM, yogu13 <yo...@gmail.com> wrote:
> Hello,
>
> I am using camel 2.14.1 in karaf with ActiveMQ 5.10. During shutdown process
> once the embedded broker is stopped, I see that graceful shutdown for routes
> having jms endpoints are taking a very long time as the endpoint are busy
> refreshing the JMS connections instead of shutting down(note: there are no
> inflight messages for processing at that point in time) and finally after a
> timeout allow the route to be destroyed and the shutdown process to proceed.
>
> JDK version being used is 1.7.x
>
> Not sure why this keeps refreshing the JMS connections instead of shutdown.
> I see that the spring provided message listener containers are used which
> could fail to interpret a shutdown.
>
> Regards,
> -Yogesh
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Graceful-Shutdown-Issue-for-JMS-endpoints-tp5767883.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/