[
https://issues.jboss.org/browse/WFLY-9222?page=com.atlassian.jira.plugin....
]
James Perkins edited comment on WFLY-9222 at 8/15/17 6:05 PM:
--------------------------------------------------------------
It looks like it has to do with the number of deployments and the size of the logging
subsystem. Since there are 100 deployments each deployment essentially gets the logging
subsystem copied to the deployments runtime resource,
{{/deployment=*/subsystem=logging}} and
{{/deployment=*/subdeployment=*/subsystem=logging}}.
I'm not really sure what the best solution would be here. I'm not even sure how
likely it would be for so many loggers to be defined and so many deployments deployed on a
single server.
{code:title=Example}
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar043.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.234
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar090.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.76
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar039.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.111
jboss.as:deployment=manyClasses.ear,subdeployment=jar048.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.176
jboss.as:deployment=manyClasses.ear,subdeployment=jar027.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.188
jboss.as:deployment=manyClasses.ear,subdeployment=jar076.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.132
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar029.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.199
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar000.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.26
jboss.as:deployment=manyClasses.ear,subdeployment=jar079.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.150
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar071.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.169
{code}
was (Author: jamezp):
It looks like it has to do with the number of deployments and the size of the logging
subsystem. Since there are 100 deployments each deployment essentially gets the logging
subsystem copied to the deployments runtime resource, {{/deployment=*/subsystem=logging}}
and {{/deployment=*/subdeployment=*/subsystem=logging}}.
I'm not really sure what the best solution would be here. I'm not even sure how
likely it would be for so many loggers to be defined and so many deployments deployed on a
single server.
{code:title=Example}
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar043.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.234
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar090.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.76
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar039.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.111
jboss.as:deployment=manyClasses.ear,subdeployment=jar048.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.176
jboss.as:deployment=manyClasses.ear,subdeployment=jar027.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.188
jboss.as:deployment=manyClasses.ear,subdeployment=jar076.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.132
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar029.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.199
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar000.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.26
jboss.as:deployment=manyClasses.ear,subdeployment=jar079.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.150
jboss.as.expr:deployment=manyClasses.ear,subdeployment=jar071.jar,subsystem=logging,configuration=default,logger=org.jboss.examples.169
{code}
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)