[
https://issues.apache.org/jira/browse/HADOOP-19668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038955#comment-18038955
]
Steve Loughran commented on HADOOP-19668:
-----------------------------------------
FWIW I"m now seeing new error messages in logs as the first time SubjectUtil is
invoked, THREAD_INHERITS_SUBJECT is coinfigured and the JRE tells me off.
{code}
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by
org.apache.hadoop.security.authentication.util.SubjectUtil
(file:/Users/stevel/.m2/repository/org/apache/hadoop/hadoop-auth/3.5.0-SNAPSHOT/hadoop-auth-3.5.0-SNAPSHOT.jar)
WARNING: Please consider reporting this to the maintainers of
org.apache.hadoop.security.authentication.util.SubjectUtil
WARNING: System::setSecurityManager will be removed in a future release
{code}
We can't have this being looked all the time, as it'll be the first thing
anyone sees on all cli commands, app launches etc.
Is there are better way to determine this? It's only setSecurityManager() which
reports this, not getSecurityManager. And on java < 22 we know the security
manager is there.
> Add SubjectInheritingThread to restore pre JDK22 Subject behaviour in Threads
> -----------------------------------------------------------------------------
>
> Key: HADOOP-19668
> URL: https://issues.apache.org/jira/browse/HADOOP-19668
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
> Affects Versions: 3.5.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> This is the first part of HADOOP-19574 which adds the compatibility code, and
> fixes Daemon, but does not replace native Thread instances.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
