[
https://issues.apache.org/jira/browse/HADOOP-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854217#action_12854217
]
Suresh Srinivas commented on HADOOP-6686:
-----------------------------------------
RPC server sends exception class name and printed stack trace in response.
Proposed change:
# if the exception is unwrapped, with the message set to the first line of
printed stack trace from response. The message is "<Server exception class
name>: <server exception message>"
#* While unwrapping, I propose removing the redundant "<exception class name>:
" from the message. Other than HDFSCli test I cannot think of a reason why an
application depends on the error string to include exception name, especially
given that the exception type that is thrown has that information already.
#. if the exception is not unwrapped, RemoteException is thrown as it is, with
printed stack trace as the message.
#* This behavior will be retained. The exception name here along with the stack
trace (albeit the server side) is useful for debugging.
> Remove redundant exception class name in unwrapped exceptions thrown at the
> RPC client
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-6686
> URL: https://issues.apache.org/jira/browse/HADOOP-6686
> Project: Hadoop Common
> Issue Type: Improvement
> Environment: At RPC client, when the exception thrown by the server
> is unwrapped, the exception message includes redundant exception class name.
> This redundant information should be removed.
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.22.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
