JMX: Difference between revisions
| Line 1: | Line 1: | ||
=External= | =External= | ||
* https://docs.oracle.com/javase/8/docs/technotes/guides/jmx | |||
* http://docs.oracle.com/javase/8/docs/technotes/guides/management/mxbeans.html | * http://docs.oracle.com/javase/8/docs/technotes/guides/management/mxbeans.html | ||
Revision as of 01:27, 17 June 2017
External
- https://docs.oracle.com/javase/8/docs/technotes/guides/jmx
- http://docs.oracle.com/javase/8/docs/technotes/guides/management/mxbeans.html
Internal
Overview
Subjects
Concepts
MXBean
An MXBean is a kind of MBean. For more details see
Open Type
The Platform MBean Server
The platform MBean server is an MBean server that is built into the JVM. It can be accessed and shared by all managed components that are running in that JVM. It can be retrieved with java.lang.management.ManagementFactory.getPlatformMBeanServer(). The platform MBean server was introduced in Java 5. javax.management.MBeanServerFactory can be used to create a different MBean server, or look up an already existing MBean server (that is not the platform server).
For a code example of how to look up the platform MBean server and how to register an arbitrary MBean to it, see
Platform MXBeans
A platform managed object is an JMX MXBean deployed on a JVM's platform MBean server. Platform MXBeans expose monitoring and management capabilities for components of the Java platform. Platform MXBeans only use a set of basic data types, so a JMX management application and the platform MBeanServer can interoperate without requiring classes for MXBean specific data types. The data types being transmitted between the management client and the JMX server are open types and this allows interoperation across versions.
Common platform MXBeans: