That is not plugable at the moment, but there is a url handler that is
queried to find the list of broker urls, you could plug in something
in there.
There is a simple example using a file url that contains the definitive list at:
org.apache.activemq.transport.failover.FailoverUpdateURIsTest#testUp
Firstly: So, there is no /real/ load balancing, right?
A client using failover, even if we use the update/rebalanceClusterxxx
broker settings, all clients COULD still all select the same broker, even if
randomize=true. So if I have 2 clients, each connected to one broker, and I
add a second br
there is no easy way to do this today out of the box.
it has be discussed many times, and there is even a name, ninja client.
Something that has all the smarts about brokers and their load and can
return a connection with some guarantees w.r.t to throughput etc.
The statistics broker makes broke
