It was supposed to be released with Java 7, but the status is Dormant. On the other hand, the same page says
Use generics in the JMX API, for example have
MBeanServer.queryNames
returnSet<ObjectName>
rather than justSet
.
and this did happen in Java 6. So, did some of the changes get in? Are there significant differences between Java 6 and Java 7 JMX implementations? Looking at Javadocs, I didn't notice any, but this only covers the API.
Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (such as printers) and service-oriented networks.
The JMX technology can be used for out-of-the-box management of the Java VM. The Java Virtual Machine (Java VM) is highly instrumented using the JMX technology. You can start a JMX agent to access the built-in Java VM instrumentation, and thereby monitor and manage a Java VM remotely.
JMX technology provides a component-based architecture for developing solutions to monitor and manage your applications, services, and resources. JMX technology is the way to instrument any application or service that was built using Java technology.
The JMX Messaging Protocol (JMXMP) connector is a configuration of the generic connector where the transport protocol is based on TCP and the object wrapping is native Java serialization.
I asked this question also to the current product manager for JMX at Oracle, Tuva Palm some times ago (September 2011), and she promised me, that JMX 2.0 is not dead and there will be a technical roadmap in Q1/2012.
However, nothing have happened until now and even worse, JSR-255, the JMX 2.0 spec (but also JSR-262, ther WebService connector stuff) has been marked as withdrawn since 2016 with the following reason:
JSR 255 specified changes to javax.management.* which were subsequently abandoned due to lack of resources, and were not included in the Java SE 6 or 7 Platforms. (The changes were distinct from other changes to javax.management.* specified by JSRs 3, 160, and 336 for inclusion in the Java SE 6 and 7 Platforms.) It was determined in 2014 that future changes to JMX technology would be specified directly by the umbrella JSR for the Java SE Platform.
So JMX 2.0 in its original form is factually dead.
Apparently, it was postponed to JDK 8, and all already made changes reverted, so JDK 7 final implementation should be the same as JDK 6.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With