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.
Regards,
Peter.
Sent from my Samsung device.
Include original message
---- Original message ----
From: Wang Weijun <weijun.w...@oracle.com>
Sent: 07/07/2016 09:47:09 am
To: Sean Mullan <sean.mul...@oracle.com>
Cc: jigsaw-dev <jigsaw-...@openjdk.java.net>; OpenJDK
<security-dev@openjdk.java.net>
Subject: Re: Strange test failure when referencing a class in a deprivileged
module
> On Jul 7, 2016, at 5:04 AM, Sean Mullan <sean.mul...@oracle.com> 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
