Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3186

Query MBean names takes forever when having many loggers and many classes

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JMX, Logging
    • Labels:
      None
    • Environment:

      Windows 7 and Windows 10

    • Steps to Reproduce:
      Hide

      1. Extract a fresh copy of WildFly
      2. Open standalone/configuration/standalone.xml and configure ~300 loggers with unique names (see attachment)
      3. Run WildFly and deploy an ear with many classes (see attachment -> 10.000 empty classes spread across 100 jar files)
      4. Open jconsole and click the MBeans tab

      Show
      1. Extract a fresh copy of WildFly 2. Open standalone/configuration/standalone.xml and configure ~300 loggers with unique names (see attachment) 3. Run WildFly and deploy an ear with many classes (see attachment -> 10.000 empty classes spread across 100 jar files) 4. Open jconsole and click the MBeans tab

      Description

      If you configure many loggers (~300) and deploy a rather big ear with many classes, it takes forever to query mbean names with
      javax.management.MBeanServer#queryNames or via. jconsoles MBeans tab.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                steffencz Steffen Czymmeck
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: