Standard transport protocols that an implementation of the JSR must support, so that different implementations will interoperate.Ī standard format for JMX connector addresses will be introduced. This JSR will define what the remote client API looks like and how it behaves. Register for notifications using the NotificationListener interface.

This means that remote clients can call the familiarMBeanServer operations and can This JSR will provide one mechanism for remote access by building on the JMX notion ofconnectors.Ī connector provides a remote client API for a JMX-based agent that is very similar to the localĬlient API. But it does not standardize the means to access these agents remotely. The JMX specification (JSR 3) currently provides the means to create Java based management agents, through standardized techniques for instrumentation, and standardized agent services. The Maintenance Lead has provided the public Issue list and communications channel for feedback.Į-Mail Address: Number: +33 4 76 18 83 52įax Number: +33 4 76 18 83 50 2.1 Please describe the proposed Specification: The following changes have been made to the original request.Į-Mail Address: hinkmond.wong Number: +1 4 Note that this JSR was completed under JCP 2.5, and moved to JCP 2.6 in Maintenance. Updates to the Original Java Specification Request (JSR) This API extends the JMX 1.2 API to provide remote access to JMX MBean servers.

$java 160 download$

Java Specification Participation Agreement version in use: 2.0 Reason: Withdrawn following Maintenance Review 3.

Java 160 download