Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6737

hawtio overwhelms server when viewing 50-60 queues (activemq tab)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.3
    • Fix Version/s: jboss-fuse-6.3-patches
    • Component/s: Hawtio
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1. Install A-MQ 6.3 R2/R3
      2. Create 60 JMS queues (e.g. t1,t2,...t60) each having a single message
      3. produced 1000 messages on t1,t2,t3,t4 and t5
      4. Logged into hawtio, set refresh rate to 1s, checked the CPU % on the server. It was in the range of 300 to 350%

      Show
      1. Install A-MQ 6.3 R2/R3 2. Create 60 JMS queues (e.g. t1,t2,...t60) each having a single message 3. produced 1000 messages on t1,t2,t3,t4 and t5 4. Logged into hawtio, set refresh rate to 1s , checked the CPU % on the server. It was in the range of 300 to 350%

      Description

      Hawtio is causing a high load on the server within the activemq tab. This occurs with a moderate load (approximately queues).

      At present the initial triage of this issue suggests it is isolated to the core HawtIO component and as a result it is being tracked in our Fuse project with component HawtIO. The use of AMQ is simply around the test case at present.

      The goal of this JIRA is exploratory in that we need to understand the behavior, how this use case fits into the current design of HawtIO and what we can do about it.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jknetl Jakub Knetl
                  Reporter:
                  rhn-support-shiggs Stephen Higgs
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: