[
https://issues.jboss.org/browse/WFCORE-3186?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-3186:
---------------------------------------
Removing either one does seem to cut the time in half which would make sense. For me it
went from about 3 minutes to 1.5 minutes. Removing both makes the response sub-second,
however there's not many names reported then. I'm basically just testing with
something like:
{code:java}
mBeanServerConnection.queryMBeans(null, null).forEach(o ->
System.out.println(o.getObjectName()))
{code}
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)