Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1987

Include destination query functionality into the product

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.3
    • JBoss A-MQ 6.3
    • None
    • None

    Description

      When a broker contains large number of destinations (thousands), HawtIO console becomes unresponsive and unusable.

      We developed a new functionality which enables folks to disable standard MBeans for most of the objects and use alternative pages and API to query destinations on the broker.

      In order to include this into the product we need to bring changes both in the broker and HawtIO components.

      API implementation on the broker is covered with https://issues.apache.org/jira/browse/AMQ-6435

      HawtIO changes are covered with https://github.com/hawtio/hawtio/issues/2200 and this additional commit https://github.com/hawtio/hawtio/commit/1d8be8f0b74a5d8ef9c8ecc031769742821090ed

      Note for testing:

      1. Create a broker with large number of destinations

      2. Turn off all but basic MBeans

      <managementContext>
      	<managementContext suppressMBean="endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationType=Queue,destinationType=Topic"/>
      </managementContext>

      3. Try to use new Queues and Topics pages accessibly from the Broker sub-tab

      Attachments

        Activity

          People

            dejanbosanac Dejan Bosanac
            dejanbosanac Dejan Bosanac
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: