Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2795C18875 for ; Thu, 11 Feb 2016 20:18:19 +0000 (UTC) Received: (qmail 26389 invoked by uid 500); 11 Feb 2016 20:18:18 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 26173 invoked by uid 500); 11 Feb 2016 20:18:18 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 25894 invoked by uid 99); 11 Feb 2016 20:18:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Feb 2016 20:18:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 3E5912C1F5D for ; Thu, 11 Feb 2016 20:18:18 +0000 (UTC) Date: Thu, 11 Feb 2016 20:18:18 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-12795) KMS does not log detailed stack trace for unexpected errors. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-12795: ----------------------------------- Status: Patch Available (was: Open) > KMS does not log detailed stack trace for unexpected errors. > ------------------------------------------------------------ > > Key: HADOOP-12795 > URL: https://issues.apache.org/jira/browse/HADOOP-12795 > Project: Hadoop Common > Issue Type: Bug > Components: kms > Reporter: Chris Nauroth > Attachments: HADOOP-12795.001.patch > > > If the KMS server encounters an unexpected error resulting in an HTTP 500 response, it does not log the stack trace. This makes it difficult to troubleshoot. The client side exception cannot provide further details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)