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

Brian Stansberry (JIRA) issues at jboss.org
Mon Aug 14 10:14:00 EDT 2017


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

Brian Stansberry commented on WFLY-9222:
----------------------------------------

[~jamezp] Is this resolved now? I know I plan further improvements in the JMX stuff for WildFly Core 4 / WildFly 12 (see WFCORE-2719), but I don't remember clearly if you did something specific to logging to help with this.

> Query MBean names takes forever when having many loggers and many classes
> -------------------------------------------------------------------------
>
>                 Key: WFLY-9222
>                 URL: https://issues.jboss.org/browse/WFLY-9222
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMX, Logging
>    Affects Versions: 10.1.0.Final
>         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)


More information about the jboss-jira mailing list