[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431460#comment-13431460
]
Suresh Srinivas commented on HADOOP-8661:
-----------------------------------------
bq. But in 23, the message doesn't have the Exception class name
(org.apache.hadoop.security.AccessControlException).
We removed this redundant information from message in HADOOP-6686. You can get
back to previous message on Oozie with:
{{exception.getClass().getName() + ": " + exception.getMessage()}}
> Stack Trace in Exception.getMessage causing oozie DB to have issues
> -------------------------------------------------------------------
>
> Key: HADOOP-8661
> URL: https://issues.apache.org/jira/browse/HADOOP-8661
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
>
> It looks like all exceptions produced by RemoteException include the full
> stack trace of the original exception in the message. This is causing issues
> for oozie because they store the message in their database and it is getting
> very large. This appears to be a regression from 1.0 behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
