Previously, if the Identity service encountered a failed connection to a message broker, re-connection attempts kept failing as well. This was because the Identity service tried to reconnect to the same failing message broker, even if there were multiple hosts configured. This has been fixed by making the reconnect() implementation select the next broker in the list. As a result, when multiple broker hosts are provided, it will try the next one in the list at every connection attempt. This means that non-failure reconnect attempts will also switch from the current broker to the next in the list. Hence, users should not rely on any particular order when using brokers from the list.