Say you are bootstrapping a cluster. The first node will have static connectors to the other nodes, and you will see this quite repetitively in the logs:

[main] 09:56:58,606 WARN [org.apache.activemq.artemis.core.client] AMQ212025: did not connect the cluster connection to other nodes
java.lang.Exception: null
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.<init>(ServerLocatorImpl.java:326) ~[classes/:?]
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.<init>(ServerLocatorImpl.java:378) [classes/:?]
at org.apache.activemq.artemis.api.core.client.ActiveMQClient.createServerLocatorWithoutHA(ActiveMQClient.java:311) ~[classes/:?]
at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:51) ~[classes/:?]
at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:33) ~[classes/:?]
at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:84) ~[classes/:?]
at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:28) ~[classes/:?]
at org.apache.activemq.artemis.utils.uri.URIFactory.newObject(URIFactory.java:59) ~[classes/:?]

This is because the connect method will log.warn when no nodes are connected, and throw an exception.

There's no need for the logger.warn in this situation as the caller will be responsible for the retry loop.