This is plenty for me to look into! Much appreciated, Joe! I shall play with these options a bit more and get back to the list either way (either with more questions or explaining how I did it). Thanks!
Joe Fernandez wrote: > > I have seen the InvalidClientIDException in these types of 'duplex' > scenarios and in most cases it is hurled because two brokers have duplex > connectors (forwarding bridges) to each other. If you can, post the > exception's stack trace and the brokers' cfg files. > > There have been duplex-related issues, so make sure you're using 5.1 and > check with the issues tracker. > > http://issues.apache.org/activemq/browse/AMQ > > In your case, you may want to keep the networkTTL to 1 since messages only > have to traverse one bridge to get to their destination. See AMQ-1661 and > AMQ-1542. > > The messaging pattern that you've described sounds a bit like a 'recipient > list'. You can implement this sort of pattern via an ActiveMQ virtual > topic or Camel. > > A virtual topic is rather neat because it is a combination of topic and > queue; you get the best of both worlds. For example, your producer sends a > message to a virtual topic called 'blast', which then broadcasts messages > out to any number of queues (e.g., QueueA, QueueB, etc.). > > http://activemq.apache.org/virtual-destinations.html > > Also see the following, which describes how to implement a recipient list > via Camel > > http://activemq.apache.org/camel/recipient-list.html > > Hope this helps. > > Joe > Get a free ActiveMQ user guide @ www.ttmsolutions.com > > > > kpalania wrote: >> >> Is this possible via ActiveMQ? >> >> * Client sends message to broker A that has no network connectors >> defined. >> * Broker B has a network connector pointing to broker A and has duplex >> set to TRUE. >> * Message is sent to a queue named "Test". >> * Consumer listening to "Test" on broker B gets the message . >> >> Now - >> * I add broker C and configure it the same way as broker B in that it >> points to broker A as well, and had duplex set to TRUE. >> * When I start broker C, I start seeing exceptions >> (InvalidClientIDException, etc). >> >> What if I want the message (sent to broker A by the client) to be >> forwarded to both brokers, broker B and broker C (to the same queue)? The >> consumers listening to the queues on brokers B and C would be configured >> such that they only dequeue messages from a specific queue. So, for >> instance, though all messages get sent to all the queues, consumer A >> listening to broker A would only dequeue messages from "Test" while >> consumer B listening to broker B would only dequeue messages from "Test >> 2". >> >> Is this possible? If yes, what should the configuration be? >> > > -- View this message in context: http://www.nabble.com/Duplex-connection%3A-Is-this-possible--tp18619648p18632526.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
