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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • JMX, Logging
    • None
    • 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

      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.

        1. manyClasses.ear
          299 kB
          Steffen Czymmeck
        2. standalone.xml
          49 kB
          Steffen Czymmeck

            Unassigned Unassigned
            steffencz_jira Steffen Czymmeck (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: