Everything JMX exposes — heap and thread beans, application metrics, the operations an app publishes for its operators — becomes readable and callable in the session, including the writes that change a running system.
A JMX front end for a Java application with a Jolokia agent attached. It lists the JVM's MBeans, lists a bean's attributes and operations, reads and writes attributes, and executes operations — over HTTP rather than through a JMX console.
- Every MBean object name in the connected JVM
- The operations and the attributes defined on a given MBean, as JSON definitions
- An attribute read, and an attribute written
- An operation executed on a bean
- Two distributions: a standalone server that connects to a JVM with a Jolokia agent, and a JVM agent that turns the application itself into the server
For the standalone distribution, a Java application with a Jolokia agent attached; the JVM Agent distribution replaces the standard Jolokia JVM agent and opens the MCP port itself. Either way it connects to a single JVM, chosen at startup.
One command — jbang org.jolokia.mcp:jolokia-mcp-server:0.5.1:runner