You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Siva Teja (healthAlliance)" <Si...@healthalliance.co.nz> on 2023/03/21 20:26:07 UTC

Duplicate network brokers as consumers

Hi,

I have activemq(5.17.4) setup within the network in total 4 pairs of brokers which acts as master slave. All of them connect to each network as below

Example of node1(akl1-mmh1)
Network Bridge
<networkConnector name="ntwrk_akl1_node2"
                              uri="masterslave:(ssl://amq-uat-mmh2.healthcare.huarahi.health.govt.nz:61617,ssl://amq-uat-akl2.healthcare.huarahi.health.govt.nz:61617)"
                              networkTTL="3"
                              conduitSubscriptions="true"
                              decreaseNetworkConsumerPriority="true"
                              suppressDuplicateQueueSubscriptions="true"
                              duplex="false"/>
            <networkConnector name="ntwrk_akl1_node3"
                              uri="masterslave:(ssl://amq-uat-mmh3.healthcare.huarahi.health.govt.nz:61617,ssl://amq-uat-akl3.healthcare.huarahi.health.govt.nz:61617)"
                              networkTTL="3"
                              conduitSubscriptions="true"
                              decreaseNetworkConsumerPriority="true"
                              suppressDuplicateQueueSubscriptions="true"
                              duplex="false"/>
            <networkConnector name="ntwrk_akl1_node4"
                              uri="masterslave:(ssl://amq-uat-mmh4.healthcare.huarahi.health.govt.nz:61617,ssl://amq-uat-akl4.healthcare.huarahi.health.govt.nz:61617)"
                              networkTTL="3"
                              conduitSubscriptions="true"
                              decreaseNetworkConsumerPriority="true"
                              suppressDuplicateQueueSubscriptions="true"
                              duplex="false"/>

Transport Connector of Node1
<transportConnector name="ssl"
                    uri="ssl://0.0.0.0:61617?transport.connectionTimeout=10000&amp;transport.trace=true&amp;transport.needClientAuth=false&amp;transport.maximumConnections=5000&amp;transport.useKeepAlive=true&amp;transport.soTimeout=60000&amp;transport.keepAlive=true&amp;wireFormat.maxFrameSize=104857600&amp;wireFormat.tightEncodingEnabled=false&amp;wireFormat.maxInactivityDuration=3600000"
                    updateClusterClients="true" updateClusterClientsOnRemove="true" enableStatusMonitor="true"/>

For some reason after a week or 2 the number of consumers keeps increasing to 10+ on each node and the messages are stuck on the queue.
Sample screenshot of above issue can be found here<https://i.stack.imgur.com/PcAMz.png>.

Is there a bug if not is there a way to find these duplicate connections and get rid of them ?

Kind Regards
--

Siva Teja


This e-mail message and any accompanying attachments may contain information that is confidential and subject to legal privilege.
If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments.
If you have received this message in error, please notify the sender immediately and delete this message.