-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b156
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8174288 | 10 | Daniel Fuchs | P2 | Resolved | Fixed | b01 |
JMX Remote API is designed to support different types of connectors to make a MBean server remotely accessible through different protocol.
java.management currently includes the JMX RMI connector, which is the standard connector for the Java SE platform (i.e. javax.management.remote.rmi package). JMX and JMX remote API does not depend on RMI at all but only JMX RMI connector does. JMX RMI connector should be separated from java.management module.
It's proposed to separate javax.management.remote.rmi into its own module named `java.management.rmi`.
java.management currently includes the JMX RMI connector, which is the standard connector for the Java SE platform (i.e. javax.management.remote.rmi package). JMX and JMX remote API does not depend on RMI at all but only JMX RMI connector does. JMX RMI connector should be separated from java.management module.
It's proposed to separate javax.management.remote.rmi into its own module named `java.management.rmi`.
- backported by
-
JDK-8174288 JMX RMI connector should be in its own module
-
- Resolved
-
- blocks
-
JDK-8173821 com.sun.jmx.remote.internal.Unmarshal should be removed.
-
- Resolved
-
- relates to
-
JDK-8173608 Separate JDK management agent from java.management module
-
- Resolved
-