[
https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143518#comment-15143518
]
Arun Suresh commented on HADOOP-12795:
--------------------------------------
[~cnauroth], Thanks for raising this..
Yup, the {{KMSExceptionsProvider#log}} method was written specifically for that
purpose.. must've missed wiring it in..
Your patch should work.. maybe you can also add the log to the other
INTERNAL_SERVER_ERROR clause as well ?
+1 pending that
> 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)
