[
https://issues.apache.org/jira/browse/HADOOP-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165066#comment-13165066
]
Sanjay Radia commented on HADOOP-7897:
--------------------------------------
{code}
* <li>Exceptions encountered on the client side in this method are
* thrown as is.
{code}
Change to
{code}
* <li>Exceptions encountered on the client side in this method are
* wrapped in ServiceException as is.
{code}
+1
> ProtobufRPCEngine client side exception mechanism is not consistent with
> WritableRpcEngine
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-7897
> URL: https://issues.apache.org/jira/browse/HADOOP-7897
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.24.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.24.0
>
> Attachments: HADOOP-7897.txt
>
>
> In ProtobufRpcEngine the client side exceptions are wrapped in
> RpcClientException. The RpcClientException is used to create RemoteException
> which is set as cause in the thrown ServiceException. However
> WritableRpcEngine throws the client encountered exception as is. This
> difference in behavior causes, many tests to fail in the existing unit tests,
> which expect the client invoker() to thrown the exception as is. This jira
> makes the ProtobufRpcEngine behavior consistent with that of
> WritableRpcEngine.
--
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
