You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2023/10/18 20:54:00 UTC

[jira] [Created] (FLINK-33309) java.security.manager is desallow by default starting in java18

Sergey Nuyanzin created FLINK-33309:
---------------------------------------

             Summary:  java.security.manager is desallow by default starting in java18
                 Key: FLINK-33309
                 URL: https://issues.apache.org/jira/browse/FLINK-33309
             Project: Flink
          Issue Type: Sub-task
            Reporter: Sergey Nuyanzin


The change was done within [https://openjdk.org/jeps/411]

{quote}
Starting in Java 18, the default value of java.security.manager will be disallow if not otherwise set via java -D.... As a result, applications and libraries that call System::setSecurityManager may fail due to an unexpected UnsupportedOperationException. In order for System::setSecurityManager to work as before, the end user will have to set java.security.manager to allow on the command line (java -Djava.security.manager=allow ...).
{quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)