[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602451#comment-15602451
]
Xiao Chen commented on HADOOP-13669:
------------------------------------
The pre-commit -1 is again on the trunk run. For the patched run, we can see
this:
{noformat}
============================================================================
============================================================================
findbugs detection: patch
============================================================================
============================================================================
....
hadoop-common-project/hadoop-kms generated 0 new + 0 unchanged - 2 fixed = 0
total (was 2)
{noformat}
So it should be fixed this time... Also verified via {{mvn compile
findbugs:findbugs}} locally.
> 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: [email protected]
For additional commands, e-mail: [email protected]
