[ https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605906#comment-15605906 ]
Hudson commented on HADOOP-13669: --------------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10673 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10673/]) HADOOP-13669. Addendum patch 2 for KMS Server should log exceptions (xiao: rev 09ef97dccbd4c11aaeedf7503d414f999435ad91) * (edit) hadoop-common-project/hadoop-kms/dev-support/findbugsExcludeFile.xml > 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