Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <33057867.72551283192755246.JavaMail.jira@thor>
Date: Mon, 30 Aug 2010 14:25:55 -0400 (EDT)
From: "Giridharan Kesavan (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-6913) Circular initialization between
 UserGroupInformation and KerberosName
In-Reply-To: <27327567.281671281550577971.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Giridharan Kesavan updated HADOOP-6913:
---------------------------------------

    Status: Patch Available  (was: Open)

> Circular initialization between UserGroupInformation and KerberosName
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-6913
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6913
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>         Attachments: c6913-01.patch
>
>
> If the first call to UGI is UGI.setConfiguration(conf), it will try to initialize UGI class. During this initialization, the code calls KerberosName.setConfiguration(). KerberosName's static initializer will in turn call UGI.isSecurityEnabled(). Since UGI hasn't been completely initialized yet, isSecurityEnabled() will re-initialize UGI with a DEFAULT conf. As a result, the original conf used in UGI.setConfiguration(conf) will be overwritten by the DEFAULT conf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.