hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13669) KMS Server should log exceptions before throwing
Date Fri, 14 Oct 2016 06:01:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574350#comment-15574350
] 

Hudson commented on HADOOP-13669:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10609 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10609/])
HADOOP-13669. Addendum patch for KMS Server should log exceptions before (xiao: rev ae51b11f7872eaac558acf00fd23f6d7b1841cfe)
* (edit) hadoop-common-project/hadoop-kms/dev-support/findbugsExcludeFile.xml


> 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
>             Fix For: 2.8.0, 3.0.0-alpha2
>
>         Attachments: HADOOP-13369.2.patch, HADOOP-13369.patch, HADOOP-13369.patch.1,
HADOOP-13669.addendum.patch, trigger.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


Mime
View raw message