Eamonn McManus's Blog

Blogging about JMX technology

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). It was defined by JSRs 3 (for the local part) and 160 (for the remote part), and continues to evolve through JSRs 255 (JMX API 2.0) and 262 (Web Services Connector for JMX Agents).

What does all this mean for future versions of the Java platform?

The current platform (5.0, Tiger) contains version 1.2 of the JMX API and version 1.0 of the JMX Remote API.

The distinction between these two APIs is mostly an accident of history, so going forward they will be combined.

The next version of the core platform (6.0, Mustang) will contain version 1.3 of the JMX API. The version after that (7.0, Dolphin) will contain version 2.0.

We try to be as open as possible about these developments. In particular, you can see what's going in detail through the bug database. A good starting point is bug 5072268. And, you can track the API changes almost in real time through the online Mustang API docs. Look out for a bunch of new stuff arriving in Build 40!

Over time I plan to talk here about the changes to the API that are planned or in progress. I'll also mention JSR 262 (Web Services Connector) from time to time. And I'll mention some tips and best practices that we've accumulated over the years working with JMX technology.

Don't hesitate to let us know what you'd like to see in the JMX API, through comments here, or in the bug database, or mailed directly to jmx-spec-comments@sun.com.

Comments

• When can we expect JMX Best Practices blog?

  Posted by: ampatil on June 09, 2005 at 03:11 AM

• I'm thrilled to see something happening on the JMX front. I thought it was a lost spec as the latest book on JMX I could find was from 2003.

  Posted by: cmcbrien on June 11, 2005 at 11:08 AM

• It's probably best not to judge a technology's health on the basis of books. Probably authors have felt that with at least six books on JMX technology the subject was pretty much covered. But the API continues to evolve, and I'll be talking about that here.

  Potential authors might like to note that only one of the books covers the latest completed version of the JMX API and none of them talk about the API as it is integrated into the JDK. So there's some room for new writings there.

  Posted by: emcmanus on June 14, 2005 at 08:13 AM

This work is licensed under a Creative Commons License.