Strange test failure when referencing a class in a deprivileged module

[Peter Firmstone]

Have you tried setting the jvm in security debug mode to see else might be occurring?  If so can you send the output?

Regards,

Peter.

Sent from my Samsung device.
 
  Include original message
---- Original message ----
From: Wang Weijun <weijun.wang at oracle.com>
Sent: 07/07/2016 11:08:58 am
To: Peter Firmstone <peter.firmstone at zeus.net.au>
Cc: SeanMullan <sean.mullan at oracle.com>; jigsaw-dev <jigsaw-dev at openjdk.java.net>; OpenJDK <security-dev at openjdk.java.net>
Subject: Re: Strange test failure when referencing a class in a deprivileged module


> On Jul 7, 2016, at 8:19 AM, Peter Firmstone <peter.firmstone at zeus.net.au> 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 <weijun.wang at oracle.com> 
> Sent: 07/07/2016 09:47:09 am 
> To: Sean Mullan <sean.mullan at oracle.com> 
> Cc: jigsaw-dev <jigsaw-dev at openjdk.java.net>; OpenJDK <security-dev at 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.mullan at 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  
>  
>