Bug ID: JDK-6425769 Allow specifying an address to bind JMX remote connector

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 7	JDK 8	JDK 9	Other
7u171Resolved	8u102Fixed	9 b103Fixed	openjdk7uFixed

A DESCRIPTION OF THE REQUEST :
Add the ability to specify a bind address for jmx remote.

JUSTIFICATION :
This is necessary to bind to a specifial address.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
java -Dcom.sun.management.jmxremote.host=myhost
ACTUAL -
jmxremote will be bound to the specified ip address or hostname

NOTE: Not critical for JDK 7 in July
13-06-2016
Done: http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-November/020717.html Thanks!
18-11-2015
Please, re-post the review request with the latest version (no changes to SslRMIServerSocketFactory) to the mailing list so we can continue in the review.
18-11-2015
Review seems to be stalled. Latest webrevs are: http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/02/ A version not involving changes to SslRMIServerSocketFactory.java: http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/03.no-rmi-ssl-factory-changes/
18-11-2015
Review thread(s) with a proposed fix: http://mail.openjdk.java.net/pipermail/jmx-dev/2015-November/000873.html http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-November/020404.html
02-11-2015
Is anybody working on this? If not, I can propose a patch for this issue.
28-10-2015
EVALUATION * we could wait for 4880793 to be fixed before implementing this RFE. In that case we could possibly use the 'host' information from the JMXServiceURL as the host IP to bind to and pass in client stubs (do we need to differenciate?). * In the shorter term we could also provide an example that would implement the workaround (see Work Around).
15-05-2006
WORK AROUND Today, the RMI registry will not let you specify an interface to which to bind to. By default it will bind to 0.0.0.0 and listen to all interfaces. Furthermore, the host value placed in the remote stub for an exported remote object is the IP address of the InetAddress returned from an invocation of the InetAddress.getLocalHost method. There's an RFE logged against RMI for this: 4880793. The desired behaviour can be achieved by starting the RMI Connector Server programmatically - instead of using the out-of-the-box System properties. To achieve the desired effect, you would have to supply customs RMI Socket Factories to the created Connector Server. More detailed informations is available in the evaluation of 4880793.
15-05-2006

Duplicate :	JDK-6440708 - JMX remote for monitoring the JVM doesn't support binding to an interface
Duplicate :	JDK-8024614 - Option to bind agent to specific interface.
Relates :	JDK-4880793 - Registry bind address flexibility
Relates :	JDK-8145982 - JMXInterfaceBindingTest is failing intermittently
Relates :	JDK-6440708 - JMX remote for monitoring the JVM doesn't support binding to an interface
Relates :	JDK-8219585 - [TESTBUG] sun/management/jmxremote/bootstrap/JMXInterfaceBindingTest.java passes trivially when it shouldn't
Relates :	JDK-8024614 - Option to bind agent to specific interface.
Relates :	JDK-8146015 - JMXInterfaceBindingTest is failing intermittently for IPv6 addresses