JDK-8022445 : fix RMISocketFactory example to avoid using localhost
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-08-06
  • Updated: 2013-10-08
  • Resolved: 2013-08-22
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 8
8 b106Fixed
Related Reports
Relates :  
JDK-8020854 - change RMI javadocs to specify that remote objects are exported to the wildcard address
Description
See discussion in this email:

http://mail.openjdk.java.net/pipermail/security-dev/2013-August/008346.html

Briefly, the example binds to a loopback address (whether IPv4 or IPv6 is unspecified, but it will be one or the other). The example suggests using localhost, which might resolve to the wrong loopback address.

The example should be changed to recommend using the appropriate IPv4 or IPv6 loopback address instead of "localhost".