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

AMQ admin console becomes unresponsive if messages are sent to topics without consumers.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • AMQ 7.11.6.GA
    • console
    • None
    • False
    • None
    • False
    • Hide

      Please create a broker instance in AMQ 7.11.6

      Please configure the Prometheus plugin.

      Please modify the configured credentials in the attached reproducer and run the reproducer.

      Try to access the AMQ broker console, the broker is slow and unresponsive, especially when navigating through the menu options as shown in the attached screenshot.

      This problem does not exist in AMQ 7.10.2. If you access the metrics page on http://localhost:8161/metrics/, the difference can be cited between the faulty broker and the healthy broker.

      The metrics page on AMQ 7.10.2 does not show the statistics of the destinations that do not have consumers, but AMQ 7.11.6 does show the statistics of the destinations that do not have consumers.

       

      Show
      Please create a broker instance in AMQ 7.11.6 Please configure the Prometheus plugin. Please modify the configured credentials in the attached reproducer and run the reproducer. Try to access the AMQ broker console, the broker is slow and unresponsive, especially when navigating through the menu options as shown in the attached screenshot. This problem does not exist in AMQ 7.10.2. If you access the metrics page on http://localhost:8161/metrics/, the difference can be cited between the faulty broker and the healthy broker. The metrics page on AMQ 7.10.2 does not show the statistics of the destinations that do not have consumers, but AMQ 7.11.6 does show the statistics of the destinations that do not have consumers.  
    • Important

      AMQ admin console becomes unresponsive if a large volume of messages are sent to topics without consumers using the MQTT protocol. This problem can be cited from AMQ 7.10.3 onwards. I did not encounter this issue on AMQ 7.10.2. 

      I was able to recreate this issue using AMQ 7.11.6. Thus, marked the said version as the affected version.

              rhn-support-jbertram Justin Bertram
              rhn-support-tywickra Tyronne Wickramarathne
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: