You could have Version 1 producers send to a different destination than Version 2 producers, and have the Version 1 consumers connect to Server 1 and the Version 2 consumers connect to Server 2. Or you could set a version number as an attribute on the message and then have the consumers use message selectors to only get the messages with the correct version. Either approach would work, and wouldn't require any special configuration in the brokers (and the producer/consumer configuration would be simple). And both of those approaches could be used without needing two separate brokers, if you didn't want to have two.
You can run multiple ActiveMQ brokers on the same machine, as long as you make sure you customize the ports so they don't conflict. Tim On Wed, Oct 1, 2014 at 8:07 AM, juanmanuel.romeraferrio < juanmanuel.romerafer...@gmail.com> wrote: > Hi, I'm new with ActiveMQ. I'm starting to use for resolve a problem in my > system. I have 1000 clients that send message to different servers. For > resolve that I thougth in an architecture with the next. > > - In the clients configure a Broker with network connector to a > master/slave > broker. > - In the master/slave broker, I need read a property of the message > "version", and according this value I need redirect the message to a > remote cluster. > > Example version 1 -Cluster 1, version2 -> Cluster 2. > > I don't know how resolve that, I thougt that I can configure a broker in > each cluster, and send the message to the master/slave cluster to the > other, > but I can't configure that, I can't start up 2 brokers in a vm, this is > rigth? > > I would need something like this > > > Client 1 (Version 1) ----message-----> Cluster master/slave broker > ------message----> Server 1 > Client 2 (Version 2) ----message-----> Cluster master/slave broker > ------message----> Server 2 > > How could it? > > > > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Question-about-Network-Brokers-tp4686054.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
