> On Jul 7, 2016, at 8:19 AM, Peter Firmstone <[email protected]> > wrote: > > Perhaps the policy provider hasn't been refreshed when the new security > manager is in force? Try doing a Policy.refresh() in the SecurityManager > constructor.
You mean Policy.getPolicy().refresh()? No difference. And I don't think this simple SecurityManager makes use of Policy at all. Thanks Max > > Regards, > > Peter. > > Sent from my Samsung device. > > ---- Original message ---- > From: Wang Weijun <[email protected]> > Sent: 07/07/2016 09:47:09 am > To: Sean Mullan <[email protected]> > Cc: jigsaw-dev <[email protected]>; OpenJDK > <[email protected]> > Subject: Re: Strange test failure when referencing a class in a deprivileged > module > > > > On Jul 7, 2016, at 5:04 AM, Sean Mullan <[email protected]> wrote: > > > > Does your SSL code match up with the stack trace? The test only has 27 > > lines, but the stack trace says it was called from line 42. > > My local SSL.java still contains the GPL comments and I didn't paste them > here. Line 42 is > > if (!(perm instanceof SQLPermission)) { > > BTW, I also tried putting the SecurityManager impl into a different codePath > with AllPermission granted, and load it on the command line with > -Djava.security.manager=X, the test still failed with the same exception. > > --Max > >
