Adding core libs. On 2.11.2015 11:38, Severin Gehwolf wrote:
Hi,Here is a patch addressing JDK-6425769. The issue is that the JMX agent binds to the wildcard address by default, preventing users to use system properties for JMX agents on multi-homed hosts. Given a host with local network interfaces, 192.168.0.1 and 192.168.0.2 say, it's impossible to start two JMX agents binding to fixed ports but to different network interfaces, 192.168.0.1:{9111,9112} and 192.168.0.2:{9111,9112} say. The JDK would bind to all local interfaces by default. In the above example to 192.168.0.1 *and* 192.168.0.2. The effect is that the second Java process would get a "Connection refused" error because another process has already been bound to the specified JMX/RMI port pairs. Bug: https://bugs.openjdk.java.net/browse/JDK-6425769 webrev: http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/00/ Testing done: jdk_jmx and jdk_management tests all pass after this change (no regressions). There is also a new JTREG test which fails prior this change and passes after. Updates to the diagnostic command have been tested manually. I understand that, if approved, the JDK and hotspot changes should get pushed together? Hotspot changes are fairly trivial since it's only a doc-update for the new JDK property in the relevant diagnostic command. Could someone please review and sponsor this change? Please let me know if there are questions. Thanks, Severin
