[
https://issues.apache.org/jira/browse/HADOOP-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-7982:
--------------------------------
Attachment: hdfs_threaded_test.c
Here's a test case which shows the issue. We tracked it down to a JNI issue --
if when using libhdfs, the thread that started the JVM isn't the same thread
that first uses libhdfs, it will fail with the error described in the JIRA. The
fix as committed solves the problem.
> UserGroupInformation fails to login if thread's context classloader can't
> load HadoopLoginModule
> ------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7982
> URL: https://issues.apache.org/jira/browse/HADOOP-7982
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.23.0, 1.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.24.0, 0.23.1, 1.1.0
>
> Attachments: hadoop-7982-branch-1.txt, hadoop-7982.txt,
> hdfs_threaded_test.c
>
>
> In a few hard-to-reproduce situations, we've seen a problem where the UGI
> login call causes a failure to login exception with the following cause:
> Caused by: javax.security.auth.login.LoginException: unable to find
> LoginModule class: org.apache.hadoop.security.UserGroupInformation
> $HadoopLoginModule
> After a bunch of debugging, I determined that this happens when the login
> occurs in a thread whose Context ClassLoader has been set to null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
