[
https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143470#comment-15143470
]
Chris Nauroth commented on HADOOP-12795:
----------------------------------------
[~jojochuang], thank you for your reply.
bq. We ended up looking at kms-catalina.log and found indirect evidence to the
root cause. Have you checked that log too?
Thanks for the suggestion, but in my case, the catalina logs were not
sufficient either. There is a record of the error in kms-audit.log, and you
can also enable request/response logging in kms.log by editing web.xml. Both
of these show the presence of an error and the short message, but nothing
provides the full stack trace for a deeper look.
bq. As for the patch, the log you added seem to be used in test only, not in
production.
I applied my patch and simulated an error by hard-coding a method to throw an
unchecked exception. With that, I could see the full stack trace in kms.log,
so I think the patch is working for the production code.
> 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)
