[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602529#comment-15602529
]
Allen Wittenauer commented on HADOOP-13669:
-------------------------------------------
I think you're still missing it:
Pre-process runs and part of it's output is this:
bq. -1 findbugs 0m 26s hadoop-common-project/hadoop-kms in trunk has 2
extant Findbugs warnings.
i.e., trunk has 2 existing findbugs issues
Yetus then starts on it's second pass with the patch in place (the mvninstall
lines are good indicators where it is). It then provides this output:
bq. +1 findbugs 0m 34s hadoop-common-project/hadoop-kms generated 0
new + 0 unchanged - 2 fixed = 0 total (was 2)
.... which indicates the patch fixed the 2 findbugs issues.
> 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]
