FreeBSD jdk15 does not read java.security?

[Nick Johnson]

While still trying to investigate this InetAddress negative caching 
problem I have, I found something a bit puzzling... If I could get someone 
else to verify, that would be great.

It looks like the 1.5.0_12-p6 JDK never reads java.security when it starts 
up.  Consequently the netaddress.cache.ttl and 
netaddress.cache.negative.ttl properties are never read and initialized, 
so the cache reverts to its defaults of caching forever... or at least 
that's my hypothesis.

I wrote a tiny Java program that does nothing other than resolve a 
hostname and ran it using truss.  Though the JVM does open a number of 
other configuration files, java.security is not one of them.  My old copy 
of 1.4.2 also does not open java.security.

It's conceivable that truss is somehow missing the system call to read 
java.security, but it does seem to be catching lots of other open 
and stat calls.

On Linux, strace shows the java.security open call happens just before the 
name resolution would happen.  On Windows, filemon shows it happens just 
after classes.jsa is read.

Can someone verify that the following program when run with the FreeBSD 
1.5 JDK results in no open calls for java.security?

Tiny test program follows.  Save it as Test.java, compile with javac 
Test.java and run it with "truss -o truss.out java -f Test", then you can 
grep truss.out for open system calls.

import java.net.*;

public class Test {
        public static void main(String[] args) throws Exception {
                InetAddress address = InetAddress.getByName("freebsd.org");
                System.out.println(address);
        }
}