[
https://issues.apache.org/jira/browse/ARTEMIS-4424?focusedWorklogId=879753&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-879753
]
ASF GitHub Bot logged work on ARTEMIS-4424:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Sep/23 14:02
Start Date: 11/Sep/23 14:02
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4610:
URL: https://github.com/apache/activemq-artemis/pull/4610
…onnected
The exception thrown by serverLocator.connect() should be all you need on
such case and the caller should then be responsible for taking appropriate
action.
Issue Time Tracking
-------------------
Worklog Id: (was: 879753)
Remaining Estimate: 0h
Time Spent: 10m
> "AMQ212025: did not connect the cluster" when bootstrapping a static cluster
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-4424
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4424
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
