I'm confused by what you're asking, so let me try to explain what I would expect, and see if that answers your questions.
You will have producers, which all connect to a broker (call it BP). That broker will have networkConnectors to the broker for Version1 consumers (BV1) and the broker for Version2 consumers (BV2); it needs both of those networkConnectors so it can send messages to either broker as needed. When Version1 consumers connect to BV1, BV1 will route a subscription request to BP, and messages from producers will flow through BP to BV1 and then to Version1 consumers. The same thing will happen on BV2 for Version2 consumers. Brokers don't listen to messages, they get subscription requests from consumers and make subscription requests to other brokers to allow messages to flow to consumers. And as long as you have duplex network connectors between your brokers and Advisory messages are enabled (as they are by default), all of the subscriptions will just work. On Thu, Oct 2, 2014 at 10:14 AM, juanmanuel.romeraferrio < juanmanuel.romerafer...@gmail.com> wrote: > Thanks for the reply, > > I have a doubt, I in my client define a broker that have a netwotk > connector > to my activeMQServer (is a name). > > In my activeMQServer, Would I need define a broker that listen this > message? > I could define a broker to listen and then then other that have netwotk > connector to send the message to other cluster? > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Question-about-Network-Brokers-tp4686054p4686102.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
