Difference between JMX and RMI

Question

What is the purpose of JMX and what is it used for? I have been scanning through some of the tutorials on JMX and all they do is register some Mbeans and invoke those Mbeans from jconsole. If that is its purpose, then what is the difference between JMX and RMI (remote procedure call)?

Thanks in advance!

Answer 1

Yes in JMX we register our objects in mbean server using the ObjectName and objectReference . We can then change attributes or invoke methods remotely.

A connector makes a Java Management Extensions (JMX) technology MBean server accessible to remote Java technology-based clients.Many different implementations of connectors are possible. In particular, there are many possibilities for the protocol used to communicate over a connection between client and server.Some Connectors defined by the JMX Remote API specification are

• " RMI Connector ": This standard Remote Method Invocation (RMI) protocol must be supported by every implementation that conforms to the JMX Remote API standard.
• " Generic Connector ": The JMX Remote API standard also defines an optional protocol based directly on TCP sockets, called the JMX Messaging Protocol (JMXMP). An implementation of the standard can omit the JMXMP connector, but must not omit the RMI connector. The Java SE platform does not include the optional JMXMP connector.
• " User-Defined Protocols ": A connector can also implement a protocol that is not defined in the JMX technology.

If you look at the above architecture a connector provides full remote access to the MBeanServer API using various communication frameworks ( RMI, IIOP, JMS, WS-* … ), while an adaptor adapts the API to another protocol (SNMP, …) or to Web-based GUI (HTML/HTTP, WML/HTTP, …).

Generally we use JMX connectors to connect to the MBean server but we can chose other connectors as well.

To sum up JMX is an java technology and RMI is for Remote Method Invocation a Java specific implementation of a Remote Procedure Call interface which can be used in the JMX to communicated remotely.

Answer 2

'Remote Procedure Call' is a distributed computing concept where a process running on one host can call a procedure on another remote host. RMI in Java is one implementation of this concept.

MBeans are bean classes that can be registered with a JMX bus to listen to events arriving on the bus or to send events on the bus or to collect various sorts of data from the other participating Mbeans etc. It is most often used for health monitoring of application servers etc. It can check the number of active connections, amount of free memory and many other statistics to an analysis engine. And yes, they can be invoked remotely using an RPC mechanism. This is vital to its functioning as data collectors since in a cluster of application servers the data has to be fetched from all the collectors and collated at one place for analysis.

Answer 3

JMX is a generic API for publishing an interface to monitor the internals of a Java application ( A Java version of SNMP ).

RMI is for Remote Method Invocation a Java specific implementation of a Remote Procedure Call interface, they are not related at all.