Increased MBeanServerImpl retention in JBoss EAP 5

Solution Verified - Updated -

Environment

  • JBoss EAP 5
    • 5.0.0
    • 5.0.1

Issue

Why is the retention in the org.jboss.mx.server.MBeanServerImpl registry (BasicMBeanRegistry) domainMap so much higher in JBoss Enterprise Application Platform (EAP) 5 (~90MB+) vs. EAP  4.2/4.3 (~20MB)?

Resolution

JBoss EAP 5.0.0 and 5.0.1 deploy optional microcontainer debug MBeans by default.

Either upgrade to EAP 5.1.0, where these MBeans are no longer deployed by default[1], or edit $JBOSS_HOME/server/$CONFIG/conf/bootstrap/deployers.xml and comment out the "Deployers" bean "annotation" directive.

Change this:

<!-- The holder for deployers that do real deployment -->
<bean name="Deployers" class="org.jboss.deployers.plugins.deployers.DeployersImpl">
    <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.deployment:service=DeployersImpl", exposedInterface=org.jboss.deployers.plugins.deployers.DeployersImplMBean.class, registerDirectly=true)</annotation>

to this:

<!-- The holder for deployers that do real deployment -->

<bean name="Deployers" class="org.jboss.deployers.plugins.deployers.DeployersImpl">
    <!--
    <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.deployment:service=DeployersImpl", exposedInterface=org.jboss.deployers.plugins.deployers.DeployersImplMBean.class, registerDirectly=true)</annotation>
    -->

[1]https://jira.jboss.org/browse/JBPAPP-4684

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.