java/128948: java/jdk16 built from source can't bind a socket, but diablo-jdk16 downloaed during build can.

[Andrew Reilly]

>Number:         128948
>Category:       java
>Synopsis:       java/jdk16 built from source can't bind a socket, but diablo-jdk16 downloaed during build can.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-java
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 17 22:40:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Reilly
>Release:        FreeBSD 7.1-PRERELEASE amd64
>Organization:
>Environment:
System: FreeBSD duncan.reilly.home 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #36: Sat Nov 15 09:26:38 EST 2008 root at duncan.reilly.home:/usr/obj/usr/src/sys/DUNCAN amd64


	Machine is an Athlon64-X2 with 2G RAM
>Description:
	Just built jdk-1.6.0.3p4_6 from ports, which had the
	effect of downloading diablo-jdk-1.6.0.07.02_2 as part
	of the build process.  I had netbeans-6.1 installed, so
	used that as a test.  Using the source-built jdk
	resulted in this error:

$ netbeans --jdkhome /usr/local/jdk1.6.0/
java.net.BindException: Can't assign requested address
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
	at java.net.ServerSocket.bind(ServerSocket.java:319)
	at java.net.ServerSocket.<init>(ServerSocket.java:185)
	at org.netbeans.CLIHandler$Server.<init>(CLIHandler.java:964)
	at org.netbeans.CLIHandler.initialize(CLIHandler.java:523)
	at org.netbeans.CLIHandler.initialize(CLIHandler.java:346)
	at org.netbeans.MainImpl.execute(MainImpl.java:180)
	at org.netbeans.MainImpl.main(MainImpl.java:75)
	at org.netbeans.Main.main(Main.java:75)

	and when netbeans started it complained of being unable
	to connect to the network.

	Using the diablo-jdk-1.6 resulted in a flawless run with
	no commentary on stderr.

>How-To-Repeat:
	Build /usr/ports/java/jdk16, then run netbeans.
>Fix:

	Don't know, sorry.  A work-around appears to be to run
	diablo-jdk instead.


>Release-Note:
>Audit-Trail:
>Unformatted: