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

[Steffen Czymmeck (JIRA)]

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

Steffen Czymmeck edited comment on WFCORE-3186 at 8/16/17 7:59 AM:
-------------------------------------------------------------------

[~jamezp] I encountered this while migrating a big application from an older JBoss version to WildFly. I guess we could reduce the number of configured loggers, but even with only a few it's still pretty slow compared to JBoss 5, where you could query MBean names nearly instantaneously.
Edit: Even with a reduced number of configured loggers (28 in my case) it is still incredibly slow. In the long run I could also reduce the number of deployments, but the performance hit would still be noticeable.


was (Author: steffencz):
[~jamezp] I encountered this while migrating a big application from an older JBoss version to WildFly. I guess we could reduce the number of configured loggers, but even with only a few it's still pretty slow compared to JBoss 5, where you could query MBean names nearly instantaneously.

> 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)