Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2896

DuplicateIDCacheImpl leak

XMLWordPrintable

      One bridge is created between each node in the cluster. The broker uses a store-and-forward queue for each bridge to move messages between brokers. However, the system is repeatedly creating new store-and-forward queues and the old store-and-forward queues are not cleaned up. This is similar to issue ENTMQBR-2700 for openshift pods that scale down and up.

      If we examine the data print, we see lots of bridge queue names, and there should be one queue per bridge connection:

      [shiggs@localhost data-print]$ grep "AddRecordTX.BRIDGE." ./broker_data_print.txt | grep -o "address=BRIDGE.*," | sort | uniq | wc -l
      79592

      It's unclear why all these bridge store and forward queues are being generated.

              rh-ee-ataylor Andy Taylor
              rhn-support-shiggs Stephen Higgs
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: