Can we have a ConnectionLoadBalancingPolicy which will start at the first connection defined in the initialConnection list and subsequently Round Robin around the list of connection urls in the ORDER they are defined.

Context:

In a scenario where:

• all the connection urls are known in advance,
• using multiple instances of org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory. For example using 4 separate connection factories with a broker cluster of 2 live brokers.

For “RoundRobinConnectionLoadBalancingPolicy" and “RandomConnectionLoadBalancingPolicy" they both start from a random point in the list. But the “random” choice could be unfavourable and clump the connections on one broker.

The “FirstElementConnectionLoadBalancingPolicy” it seems to always return the first connection in the list.

In Openwire there was an option of trying a list of urls in order (starting from the first). If there was a known fixed set of clients, you could change the order of urls on different clients to spread the load.