camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Master Slave Camel-ActiveMQ
Date Fri, 03 Jan 2014 02:17:14 GMT
There is one shortcoming of the Zookeeper policy, the route is started before the route policy
get a chance to stop the consumer.

If you are using JBoss Fuse, you can try to camel master component[1], it just starts the
master component at the first place.

[1]https://access.redhat.com/site/documentation/en-US/JBoss_Fuse/6.0/html/EIP_Component_Reference/files/Master.html

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On January 3, 2014 at 9:43:13 AM, Preethi (preethi.krishnan14@gmail.com) wrote:
>  
> I have been trying to use zookeeper but it looks like the camel  
> route on the
> slave, which is subscribing to the IBM MQ,still runs. I could  
> see the
> exception below when I start the slave.
>  
> Cause: JMSWMQ0026: Failed to subscribe to topic '#/#/ITEM/MAINT'  
> using
> MQSUB.; nested exception is com.ibm.mq.MQException: JMSCMQ0001:  
> WebSphere MQ
> call failed with compcode '2' ('MQCC_FAILED') reason '2429'  
> ('MQRC_SUBSCRIPTION_IN_USE').
>  
> This means that the slave is connecting the IBM MQ even with the  
> zookeeper
> route policy enabled. Is there a way I can have a single route running  
> at a
> time among multiple similar routes?
>  
>  
>  
> --
> View this message in context: http://camel.465427.n5.nabble.com/Master-Slave-Camel-ActiveMQ-tp5745360p5745453.html
 
> Sent from the Camel - Users mailing list archive at Nabble.com.  
>  


Mime
View raw message