[
https://issues.apache.org/jira/browse/NIFI-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766018#comment-17766018
]
ASF subversion and git services commented on NIFI-12072:
--------------------------------------------------------
Commit cbf5bb98f9a5c835e2a72f7c383e73f4c2187429 in nifi's branch
refs/heads/main from Joe Witt
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cbf5bb98f9 ]
NIFI-12072 moved to StackWalker API elimnating usage of SecurityManager (#7742)
> Move to StackWalker API to avoid the no longer allowed SecurityManager in
> Java 18+
> ----------------------------------------------------------------------------------
>
> Key: NIFI-12072
> URL: https://issues.apache.org/jira/browse/NIFI-12072
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joe Witt
> Assignee: Joe Witt
> Priority: Major
> Fix For: 2.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With NiFi 1.x we used a SecurityManager as part of our Nar Context Class
> Loading jailing process whereby even spawned threads we'd find the right
> classloader and pin the context. Java 21 makes this no longer acceptable so
> we need a new solution.
> Enter the StackWalker API https://bugs.openjdk.org/browse/JDK-8043814
> Using this we can move to a more efficient and better go forward model that
> is Java 21+ friendly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
