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?
Justin On Tue, May 28, 2024 at 3:01 PM William Crowell <wcrow...@perforce.com.invalid> wrote: > Justin, > > I do not think I have that situation: > > … > <cluster-connections> > <cluster-connection name="my-cluster"> > <connector-ref>artemis</connector-ref> > <message-load-balancing>ON_DEMAND</message-load-balancing> > <max-hops>1</max-hops> > <static-connectors> > <connector-ref>node0</connector-ref> > <connector-ref>node1</connector-ref> > </static-connectors> > </cluster-connection> > </cluster-connections> > … > > Regards, > > William Crowell > > From: Justin Bertram <jbert...@apache.org> > Date: Tuesday, May 28, 2024 at 3:57 PM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: AMQ222139 > > Where would I see if I had multiple cluster connections to the same nodes > using overlapping addresses? Would that be in broker.xml? > > Yes. That would be in broker.xml. > > > Justin > > On Tue, May 28, 2024 at 2:39 PM William Crowell > <wcrow...@perforce.com.invalid> wrote: > > > Justin, > > > > Where would I see if I had multiple cluster connections to the same nodes > > using overlapping addresses? Would that be in broker.xml? > > > > I thought I was running into this, but we do not use temporary queues: > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FARTEMIS-1967&data=05%7C02%7CWCrowell%40perforce.com%7C3926f7877093471d34e908dc7f507079%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638525230677927126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=oubjIjXoRYG6iO7Ugiei6%2BgRmFZrFJGjIbXvnuvOnvg%3D&reserved=0 > <https://issues.apache.org/jira/browse/ARTEMIS-1967> > > > > This is Artemis 2.33.0. > > > > Regards, > > > > William Crowell > > > > From: Justin Bertram <jbert...@apache.org> > > Date: Tuesday, May 28, 2024 at 1:29 PM > > To: users@activemq.apache.org <users@activemq.apache.org> > > Subject: Re: AMQ222139 > > 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. > > > > > > > > > > > > CAUTION: This email originated from outside of the organization. Do not > > click on links or open attachments unless you recognize the sender and > know > > the content is safe. > > > > > > 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. > > > > > > > CAUTION: This email originated from outside of the organization. Do not > click on links or open attachments unless you recognize the sender and know > the content is safe. > > > 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. > >
