[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602574#comment-15602574
]
Xiao Chen commented on HADOOP-13669:
------------------------------------
Thanks for the quick response [~aw]! (And sorry for not being clear above)
I believe what you described is addendum 2: trunk has 2 existing, patch fixed
the 2. So as soon as addendum 2 is reviewed, we can commit... right?
My last comment was for a postmodern on the previously-committed addendum 1. It
says trunk has 2 existing, patch passed (but without the explicit (0-2=0)
message), so I misunderstood it and thought it fixed the issue.... my bad.
> 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.addendem2.patch,
> HADOOP-13669.addendum.patch, trigger.02.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
