I'm still struggling to figure out how this is going to work in my bizarre setup.
The JMS Bridge is currently pulling from an MQ queue then transferring to a Virtual Destination which has another MQ queue defined as a destination. In other words ActiveMQ is doing all the transfer work by pulling from 1 queue and putting to another. This works fine using JMS bridging and the pure master-slave setup, but I can't figure out how to create comparable camel routes to do the same thing as the JMS Bridging. When I try to use camel routes to do the same thing as the JMS bridge the routes come up active on both the master and slave. I can't get them to only work on the master, then fail over to the slave if the master gets killed. Thanks for the any help! James.Strachan wrote: > > 2008/12/3 Stephen J <[EMAIL PROTECTED]>: >> >> I think I need to explain what I'm trying to do in more detail. I want to >> use >> ActiveMQ as a broker between two MQ series message queues. I can do this >> with JMS bridging in a master/slave configuration. >> >> However, I saw that JMS bridging is being deprecated, so I was going to >> use >> camel routes instead, as was suggested to another user on the forums. The >> master/slave part using camel routes doesn't work like the JMS bridging. >> >> With JMS bridging only 1 server at a time is brokering the messages >> between >> the MQ queues. With the camel routes, both the master and the slave come >> up >> with live routes, so either one could be brokering messages between the >> queues. > > Hosting the Camel route inside master and slave will indeed run those > routes on both JVMs. However if you are connecting to the brokers via > TCP with failover (as I described in a previous mail in this thread) - > the routes running in the slave JVM will actually connect to the > master. > > >> I can't use the ActiveMQ failover transport because I don't control the >> clients or the MQ servers. >> The only thing I can control is the ActiveMQ >> broker between the two MQ servers. > > So > > (i) configure your ActiveMQ brokers master/slave and > (ii) configure the camel routes to use failover to the 2 brokers > using TCP as I described in the previous mail > > >> The issue I am concerned about is setting up JMS bridging then having >> that >> deprecated in new versions of ActiveMQ and not being able to do the same >> things with camel routes. I really would like to use Camel routes because >> of >> the great power and flexibility of Camel. > > Camel is never gonna be deprecated so moving to it will be a great choice > :) > >> Sorry if I didn't make this clear before. I appreciate your help on this. >> >> I think ActiveMQ and Camel are some of the best pieces of software I have >> ever seen. Thanks to all who have worked on these products. > > Thanks! > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > > -- View this message in context: http://www.nabble.com/EIPs-in-the-ActiveMQ-broker-and-clustering-tp12486255p20843368.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
