[ https://issues.apache.org/jira/browse/HADOOP-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006864#comment-14006864 ]
Hudson commented on HADOOP-10562: --------------------------------- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1781/]) HADOOP-10562. Fix CHANGES.txt entry again (arp: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1596386) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt HADOOP-10562. Fix CHANGES.txt (arp: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1596378) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt > Namenode exits on exception without printing stack trace in > AbstractDelegationTokenSecretManager > ------------------------------------------------------------------------------------------------ > > Key: HADOOP-10562 > URL: https://issues.apache.org/jira/browse/HADOOP-10562 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 1.2.1, 2.4.0 > Reporter: Suresh Srinivas > Assignee: Suresh Srinivas > Priority: Critical > Fix For: 3.0.0, 1.3.0, 2.4.1 > > Attachments: HADOOP-10562.1.patch, HADOOP-10562.branch-1.1.patch, > HADOOP-10562.patch > > > Not printing the stack trace makes debugging harder. -- This message was sent by Atlassian JIRA (v6.2#6252)