Suppose (to take my favourite example), you have some sort of
cache, and you want to be able to control it via an MBean. You
might have something a bit like this:
One of the changes we made in version 1.1 of the JMX API, way back in early 2002, was to modify the serialization of certain classes. Because remote access was not part of the API at this time, this aspect had been a bit neglected in version 1.0, with the result that certain classes had underspecified or inefficient serial forms.
The short answer is: you can, but you probably shouldn't.
To be clear, here's the sort of thing I'm talking about:
JavaOne is always a huge buzz, and this year was no exception. Of
course the technical sessions are very worthwhile, so it's great news
that slides and audio for all of them will be available free online.
In previous years you had to pay a small subscription fee to access
This article by D J Walker-Morgan covers how to use JConsole to see VM information, and especially how to write an MBean and attach JConsole to check it out. The only weird thing is the idea of calling a class WatchMeMBean and the corresponding MBean interface WatchMeMBeanMBean.
We've posted a detailed set of guidelines for using the JMX API, the result of several years' experience with it.
Starting from the JMX Technology Home Page at http://java.sun.com/jmx, you can now find a link "JMX Best Practices" in the navigation bar at the left, leading you to the detailed
I'm the Specification Lead for Java Management Extensions (JMX) technology and I expect to be talking about it quite a bit in this blog. The JMX API is part of the core Java platform as of Tiger (5.0).
I'm the Specification Lead for Java Management Extensions (JMX) technology and I expect to be talking about it quite a bit in this blog.
The JMX API is part of the core Java platform as of Tiger (5.0).