[
https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143823#comment-15143823
]
Hudson commented on HADOOP-12795:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9286 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9286/])
HADOOP-12795. KMS does not log detailed stack trace for unexpected (cnauroth:
rev 70c756d35e6ed5608ce82d1a6fbfb02e19af5ecf)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSExceptionsProvider.java
> 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
> Assignee: Chris Nauroth
> Labels: supportability
> Fix For: 2.8.0
>
> Attachments: HADOOP-12795.001.patch, HADOOP-12795.002.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)
