As far as I know the only conditions that would result in this situation are described in the warning message.
Do you have multiple cluster connections to the same nodes using overlapping addresses? Do you have a way to reproduce this? Can you elaborate at all on the configuration, use-case, etc. which resulted in this? What has been the impact? Lastly, what version of ActiveMQ Artemis are you using? Justin On Tue, May 28, 2024 at 7:40 AM William Crowell <wcrow...@perforce.com.invalid> wrote: > Hi, > > What would cause AMQ222139? I have max-hops set to 1. > > 2024-05-24 17:28:04,155 WARN [org.apache.activemq.artemis.core.server] > AMQ222139: MessageFlowRecordImpl > [nodeID=2135063f-0407-11ef-9fff-0242ac110002, > connector=TransportConfiguration(name=artemis, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)?port=61617&host=mqtt-7727-node1-boxview-internal, > queueName=$.artemis.internal.sf.my-cluster.2135063f-0407-11ef-9fff-0242ac110002, > queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.2135063f-0407-11ef-9fff-0242ac110002, > postOffice=PostOfficeImpl > [server=ActiveMQServerImpl::name=mqtt-7727-node1.boxview.internal], > temp=false]@3548f813, isClosed=false, reset=true]::Remote queue binding > fa28ea36-19f2-11ef-b6bc-0242ac1100029a5d5fea-03fb-11ef-acb5-0242ac110002 > has already been bound in the post office. Most likely cause for this is > you have a loop in your cluster due to cluster max-hops being too large or > you have multiple cluster connections to the same nodes using overlapping > addresses > > Regards, > > Bill Crowell > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
