[jboss-jira] [JBoss JIRA] (WFCORE-3186) Query MBean names takes forever when having many loggers and many classes

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450226#comment-13450226 ] 

Brian Stansberry commented on WFCORE-3186:
------------------------------------------

As a workaround you can reduce the number of mbeans by dropping JMX domains that are not relevant to you:

{code}
        <subsystem xmlns="urn:jboss:domain:jmx:1.3">
            <expose-resolved-model/>
            <expose-expression-model/>
            <remoting-connector/>
        </subsystem>
{code}

Using both "expose-resolved-model" and "expose-expression-model" results in two mbeans per management resource, the latter one with attributes exposed a strings, to account for the fact that, for example, an Integer attribute may be configured with a string expression (e.g. "${foo}"). The former one provides an Integer if its possible to resolve the attribute.

If you don't need both representations you can remove one, or even remove both.

> Query MBean names takes forever when having many loggers and many classes
> -------------------------------------------------------------------------
>
>                 Key: WFCORE-3186
>                 URL: https://issues.jboss.org/browse/WFCORE-3186
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: JMX, Logging
>         Environment: Windows 7 and Windows 10
>            Reporter: Steffen Czymmeck
>         Attachments: manyClasses.ear, standalone.xml
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)