Re: -Djava.security.manager=problems for service provider

2018-03-29 Thread Naoto Sato
Hi Peter/Sean, It does seem a regression. Thanks for letting me know. I will file an issue and work on it. Naoto On 3/29/18 10:30 AM, Sean Mullan wrote: Copying Naoto. Naoto, the regression mentioned below that is causing the NPE looks to be caused by changes to java.util.ResourceBundle

Re: -Djava.security.manager=problems for service provider

2018-03-29 Thread Sean Mullan
Copying Naoto. Naoto, the regression mentioned below that is causing the NPE looks to be caused by changes to java.util.ResourceBundle in https://bugs.openjdk.java.net/browse/JDK-8182601 Can you take a look and file a bug, if so? Thanks, Sean On 3/29/18 4:53 AM, Peter wrote: Hello Java

Re: -Djava.security.manager=problems for service provider

2018-03-29 Thread Peter
Hello Java security people! It turns out we needed the -Djava.security.manager= option at startup after all... According to our SecurityManager implementation notes, the reason it instantiated the policy, was to ensure that the JVM had loaded all necessary classes, to prevent recursive

Re: -Djava.security.manager=problems for service provider

2018-03-27 Thread Peter
It would be more correct to say, it wasn't noticed until recently. The logger was recently added to our policy implementation as a todo item, previously it went to System.out.err. The logger in our security manager, while a static field, has this comment: /** * Logger is lazily loaded,