Question

I’ve been trying to get a sample JMX MXBean working in a Spring-configured webapp, but any basic attributes on the MXBean are coming up as UNDEFINED when I connect with jconsole.

Java interface/classes:

public interface IJmxBean { // marker interface for spring config, see below
}

public interface MgmtMXBean { // lexical convention for MXBeans - mgmt interface
    public int getAttribute();
}

public class Mgmt implements IJmxBean, MgmtMXBean { // actual JMX bean
    private IServiceBean serviceBean;    // service bean injected by Spring
    private int attribute = 0;

    @Override
    public int getAttribute() {
        if(serviceBean != null) {
            attribute = serviceBean.getRequestedAttribute();
        }
        return attribute;
    }

    public void setServiceBean(IServiceBean serviceBean) { 
        this.serviceBean = serviceBean;
    }
}

Spring JMX config:

<beans>
    <context:component-scan base-package="...">
        <context:include-filter type="assignable" expression="...IJmxBean" />
    </context:component-scan>
    <context:mbean-export />
</beans>

Here’s what I know so far:

• The element is correctly instantiating a bean named “mgmt”. I’ve got logging in a zero-argument public constructor that indicates it gets constructed.

• is correctly automatically detecting and registering the MgmtMXBean interface with my Tomcat 6.0 container. I can connect to the MBeanServer in Tomcat with jconsole and drill down to the Mgmt MXBean.

• When examining the MXBean, “Attribute” is always listed as UNDEFINED, but jconsole can tell the correct type of the attribute. Further, hitting “Refresh” in jconsole does not actually invoke the getter method of “Attribute”- I have logging in the getter method to indicate if it is being invoked (similar to the constructor logging that works) and I see nothing in the logs.

At this point I’m not sure what I’m doing wrong. I’ve tried a number of things, including constructing an explicit Spring MBeanExporter instance and registering the MXBean by hand, but it either results in the MBean/MXBean not getting registered with Tomcat’s MBean server or an Attribute value of UNDEFINED.

For various reasons, I’d prefer not to have to use Spring’s @ManagedResource/@ManagedAttribute annotations.

Is there something that I’m missing in the Spring docs or MBean/MXBean specs?

Answer 1

ISSUE RESOLVED: Thanks to prompting by Jon Stevens (above), I went back and re-examined my code and Spring configuration files:

Throwing an exception in the getAttribute() method is a sure way to get “Unavailable” to show up as the attribute’s value in JConsole. In my case:

• The Spring JMX config file I was using was lacking the default-autowire="" attribute on the root <beans> element;
• The code presented above checks to see if serviceBean != null. Apparently I write better code on stackoverflow.com than in my test code, since my test code wasn’t checking for that. Nor did I have implements InitializingBean or @PostConstruct to check for serviceBean != null like I normally do on almost all the other beans I use;
• The code invoking the service bean was before the logging, so I never saw any log messages about getter methods being entered;
• JConsole doesn’t report when attribute methods throw exceptions;
• The NPE did not show up in the Tomcat logs.

Once I resolved the issue with serviceBean == null, everything worked perfectly. Regardless, +1 to Jon for providing a working demo, since there are literally 50 different ways to configure MBeans/MXBeans within Spring.