JDK-6613334 : JDK.Deploy.Plugin2: Connect to local HOSTNAME (Lookup)
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u5
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2007-10-05
  • Updated: 2010-04-04
  • Resolved: 2007-12-18
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 6 JDK 7
6u10Resolved 7Resolved
Related Reports
Duplicate :  
Description
I found the odd thing, why it's not working now,
but worked before ..

I had a misconfigured 'HOSTNAME' in my /etc/hosts file,
i.e. my laptop with hostname 'ebony' had an hard entry in 
/etc/hosts which was just wrong.

The plugin seems to try to make a connection to HOSTNAME,
instead of 'localhost', which would always work.

+++

kbr:
Note that the code 
(src/plugin/share/classes/sun/plugin2/message/transport/SocketTransport.java) 
is already using InetAddress.getLocalHost(), which must be doing this 
lookup internally. I'm not sure what the correct workaround is (i.e., 
whether "127.0.0.1" is guaranteed to work, or whether we should pass in 
"localhost", etc.)

+++

Seems like, getLocalHost() is not using 'localhost' ..

Well, for our purposes, using 'localhost' on all unix machines should be good enough,
since it is mandatory .. right ?

We also could use unix domain sockets .. if they are supported within Java.

Let's see ..

Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u5/6613334.0
2007-12-18