[
https://issues.apache.org/jira/browse/PHOENIX-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890013#comment-17890013
]
Istvan Toth commented on PHOENIX-7418:
--------------------------------------
This is the error on the CI:
{{Error occurred during initialization of VM
java.lang.InternalError: Could not create SecurityManager: allow
at sun.misc.Launcher.<init>(Launcher.java:106)
at sun.misc.Launcher.<clinit>(Launcher.java:54)
at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1444)
at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1429)}}
> SystemExitRule errors out because of SecurityManager deprecation / removal
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-7418
> URL: https://issues.apache.org/jira/browse/PHOENIX-7418
> Project: Phoenix
> Issue Type: Bug
> Components: core, test
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
> Fix For: 5.3.0, 5.1.4, 5.2.2
>
>
> I have recently tried building Phoenix with Java 21, and tests have failed
> with a SecurityManager deprecation error.
> We only refer SecurityManager in SystemExitRule and TestSecurityManager.
> For the short term, we may have to simply re-enable SecurityManager in our
> tests JVMs, as our dependencies may have similar unsolved issues with Java 21.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
