[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated HADOOP-19574:
---------------------------------
Description:
Java 22 breaks Subject propagation for new Threads (when SecurityManager is not
enabled).
Previously, the Subject set by Subject.doAs() / Subject.callAs() automatically
propagated to any new Threads created (via new Thread(), not Executors).
With JDK22, this is no longer the case, new Threads do NOT inherit the Subject.
As Hadoop heavily relies on the original behavior, we somehow need to solve
this problem.
was:
Java 22 breaks Subject propagation for new Threads (when SecurityManager is not
enabled).
Previously, the Subject set by Subject.doAs() / Subject.callAs() automaatically
propagated to any new Threads created (via new Thread(), not Executors).
With JDK22, this is no longer the case, new Threads do NOT inherit the Subject.
As Hadoop heavily relies on the original behavior, we somehow need to solve
this problem.
> Restore Subject propagation semantics for Java 22+
> --------------------------------------------------
>
> Key: HADOOP-19574
> URL: https://issues.apache.org/jira/browse/HADOOP-19574
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
>
> Java 22 breaks Subject propagation for new Threads (when SecurityManager is
> not enabled).
> Previously, the Subject set by Subject.doAs() / Subject.callAs()
> automatically propagated to any new Threads created (via new Thread(), not
> Executors).
> With JDK22, this is no longer the case, new Threads do NOT inherit the
> Subject.
> As Hadoop heavily relies on the original behavior, we somehow need to solve
> this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
