MXBeans include a way to handle inter-MBean references
conveniently. You can use this to build an MBean hierarchy that
is simple to navigate.
In a previous
blog entry, I described MXBeans. User-defined
MXBeans are a new feature in the Mustang (Java SE 6) platform.
They define a type mapping, so you can use arbitrary
types in the Java interface that defines your...
The Java compiler doesn't save parameter names in the class files it generates. This is a problem for Standard MBeans, because we'd like to show those names in management clients. I talked about this in an earlier blog entry, where I suggested using a @PName annotation on each parameter to specify its name redundantly. Here's another approach, using annotation processors, which will work...
Mustang (Java SE 6) includes the ability to give additional
information about MBeans to management clients via
Descriptors, as I described previously.
But what if you are not yet able to migrate to the Mustang
platform? As I hinted in that previous entry, all is not
lost. You can still use Descriptors, though it's more work.
We often hear from developers that they'...
JDK 5.0 allows you to make an application monitorable without
writing any extra code, using command-line properties such as
-Dcom.sun.management.jmxremote. But what if the behaviour
obtained using these properties isn't exactly what you want?
Monitoring available out of the box
JDK 5.0 (codenamed Tiger) introduced support for management and
monitoring through three...