Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 1 Oct 2016 20:43:21 +0000 (UTC)
From: "Suraj Acharya (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13008772.1475195981000.715988.1475354601155@Atlassian.JIRA>
In-Reply-To: <JIRA.13008772.1475195981000@Atlassian.JIRA>
References: <JIRA.13008772.1475195981000@Atlassian.JIRA> <JIRA.13008772.1475195981608@arcas>
Subject: [jira] [Updated] (HADOOP-13669) KMS Server should log exceptions
 before throwing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 01 Oct 2016 20:43:23 -0000


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

Suraj Acharya updated HADOOP-13669:
-----------------------------------
    Status: Patch Available  (was: Open)

> KMS Server should log exceptions before throwing
> ------------------------------------------------
>
>                 Key: HADOOP-13669
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13669
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: kms
>            Reporter: Xiao Chen
>            Assignee: Suraj Acharya
>              Labels: supportability
>         Attachments: HADOOP-13369.patch
>
>
> In some recent investigation, it turns out when KMS throws an exception (into tomcat), it's not logged anywhere and we can only see the exception message from client-side, but not the stacktrace. Logging the stacktrance would help debugging.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org