Yes it is round robin and it cannot be configured. The <connection-load-balancing-policy-class-name> doesn't work becaused it is used to control how a client creates connections to a hornetq cluster.
For your case I think you can use a Topic with 10 subscribers. each subscriber has a unique selector. On your producer side for each message you can set a property with a value that randomly picked up to match one of the selectors.
Thank you very much, this answers my question!
Does the original order depend on when a client makes a connection? So if client 1 connects first, then client 2 connects 1 second later, then client 3 connects 1 second after that, will the order of the round-robin be 1-2-3-1-2-3, etc.?
yes, but remember there are other factors that may come into play such as consumer flow control, consumer buffering etc.
Understood. Thank you.