What are the characteristics of a well-designed JMX MBean

Question

What are some of the best practices in designing a JMX MBean? Any examples of ones you feel are especially useful?

Answer 1

Return absolute counts instead of rates. e.g. return total number of db commits, rather than deriving a rate.

By doing this, your clients can monitor and derive rates themselves, over whatever time periods they require. Perhaps more importantly, this protects the clients from missing surges in rates if they only connect infrequently.

If you're using JMX beans primarily via the HTML interface, then there are several practises I follow. The below often means that your JMX bean should wrap an existing bean (as opposed to just JMX-exposing existing methods):

1. output properly formatted strings representing returned objects. Getting a default toString() output can be next to useless
2. capture and display exceptions. Otherwise you'll likely get a blank page and have to go to the log files to determine what went wrong
3. if you're displaying different character sets, you may have to escape the output appropriately to prevent display problems (I ran into this with a JMX control displaying our Chinese data)
4. inputs to exposed methods should be sanitised properly (e.g. if you input a id as part of an operation you may wish to trim() it to remove whitespace etc.)

The above changes the emphasis from a bean simply exposed via JMX to something approaching a useable admin console.