[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569758#comment-15569758
]
Xiao Chen commented on HADOOP-13669:
------------------------------------
{noformat}
============================================================================
findbugs detection: trunk
============================================================================
...
hadoop-common-project/hadoop-kms in trunk has 2 extant Findbugs warnings.
============================================================================
findbugs detection: patch
============================================================================
============================================================================
cd /testptch/hadoop/hadoop-common-project/hadoop-kms
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch
-DskipTests test-compile findbugs:findbugs -DskipTests=true >
/testptch/hadoop/patchprocess/patch-findbugs-hadoop-common-project_hadoop-kms.txt
2>&1
Elapsed: 0m 21s
Starting with
/testptch/hadoop/patchprocess/branch-findbugs-hadoop-common-project_hadoop-kms-warnings.xml
Merging
/testptch/hadoop/patchprocess/patch-findbugs-hadoop-common-project_hadoop-kms-warnings.xml
Writing
/testptch/hadoop/patchprocess/combined-findbugs-hadoop-common-project_hadoop-kms.xml
{noformat}
The addendum patch fixed the errors. I think this is ready for commit, [~aw]
could you take a look? Thanks a lot.
> 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.addendum.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]
