You have to define "busy" first. If you look at an ActiveMQ instance, take a snapshot of e.g. its heapspace usage and decide that it is busier that some other instance, by the time you send the message the broker may not fit your definit
You say you want one consumer to connect to two brokers and consume one message -well a consumer is registered on a destination, so you are talking about two consumers, I think. I would be interested to know what real-world problem you are trying to solve? Sometimes our brokers dispatch of the order of 10^7 messages per minute, but we wouldn't consider them to be busy in the sense of "out of resources". There are strategies for Producer Flow Control for example, depending on the real-world problem you are trying to solve. You asked for a description... I would start with the Network of Brokers pages: http://activemq.apache.org/networks-of-brokers.html You might find this illuminating also: http://activemq.apache.org/clustering.html ----- Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View this message in context: http://activemq.2283324.n4.nabble.com/One-consumer-One-producer-many-brokers-queue-tp4652908p4652910.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
