On 21:22 Thu 02 Dec , Anthony Petrov wrote: > On 12/2/2010 7:50 PM, Pavel Tisnovsky wrote: > >> Looks like this is a problem with your patched IcedTea jtreg harness > >> rather than with the test itself then. > > > > The same behaviour could be also reported on unpatched JTreg Harness 4.0. > > > > (so it's just another reason to update JTreg harness to 4.1 on IcedTea6 ;) > > So are you saying that jtreg 4.1 works correctly, and this issue is > specific to version 4.0 only? > > -- > best regards, > Anthony
I don't think this is anything to do with jtreg, given that the default SecurityManager (created by new SecurityManager) does not allow everything, as you claimed earlier. See http://mail.openjdk.java.net/pipermail/awt-dev/2010-December/001480.html Does 4.1 install a more permissive SecurityManager or policy than that supplied by java.lang.SecurityManager and java.policy? -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Support Free Java! Contribute to GNU Classpath and IcedTea http://www.gnu.org/software/classpath http://icedtea.classpath.org PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint = F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
