-
Bug
-
Resolution: Cannot Reproduce
-
Undefined
-
None
-
AMQ 7.11.1.GA
-
None
-
False
-
None
-
False
-
-
-
-
-
Moderate
In a cluster configuration for a single share-store HA pair (needed for backup announcement / failover on shutdown behavior), if initial-connect-attempts is configured on the cluster connection, the following stack is observed continuously at roughly 10-second intervals, even after the backup has entered the cluster and announced:
2023-07-26 11:33:46,718 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:313) ~[artemis-core-client-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.<init>(ServerLocatorImpl.java:365) ~[artemis-core-client-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.api.core.client.ActiveMQClient.createServerLocatorWithHA(ActiveMQClient.java:368) ~[artemis-core-client-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.cluster.ClusterController.addClusterConnection(ClusterController.java:220) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.cluster.ClusterManager.deployClusterConnection(ClusterManager.java:642) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.cluster.ClusterManager.deploy(ClusterManager.java:249) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:3267) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.impl.SharedStoreLiveActivation.run(SharedStoreLiveActivation.java:66) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:710) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:607) ~[artemis-server-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:66) ~[artemis-cli-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:129) ~[artemis-cli-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:212) ~[artemis-cli-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:162) ~[artemis-cli-2.28.0.redhat-00003.jar:2.28.0.redhat-00003] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:144) ~[artemis-boot.jar:2.28.0.redhat-00003] at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:61) ~[artemis-boot.jar:2.28.0.redhat-00003]
The cluster seems otherwise to be correctly formed.