Bug 165957

java/jdk16 with IPV6 enabled in configuration caused ipv4 to be disabled.  Many applications which used the network all failed, unless dealing with ipv6 addresses.  A test case of creating a connected socket and outputting the exception showed an invalid parameter was being passed to a socket call, which lead to the discovery that only ipv4 addresses were affected by this issue.

Fix: 

Rebuilding the port without IPV6 has fixed IPV4, but now I cannot of course use IPV6.  Thankfully, I didn't really NEED it (not like I NEED IPv4 anyway :P).
How-To-Repeat: Built and installed java/jdk16 from ports inside a jail on a build machine, with IPV6, WEB, POLICY, TZUPDATE, and JAIL selected in the configuration.  Installed on two machines with the same effect (no ipv4).

Namely, the following test program and methodology was used to diagnose the problem:

Started netcat listeners like so:
$ nc -lk 127.0.0.1 2000
$ nc -lk ::1 2000

//
// test.java
// built with javac test.java
// ran with java test
//

import java.net.*;

public class test {
    public static void main(String argv[])
    {
	try {
            // This line was modified to be 127.0.0.1 to test ipv4
	    new Socket("::1", 2000);
	    System.out.println("Success");
	} catch (Exception e) {
	    e.printStackTrace();
	}
    }
}

//
// end test.java
//