You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/07/10 18:44:04 UTC
[jira] Resolved: (HADOOP-266) RPC doesn not handle exceptions
correctly
[ https://issues.apache.org/jira/browse/HADOOP-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-266.
----------------------------------
Resolution: Won't Fix
The code is working correctly and there are substantial problems with changing it.
> RPC doesn not handle exceptions correctly
> -----------------------------------------
>
> Key: HADOOP-266
> URL: https://issues.apache.org/jira/browse/HADOOP-266
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Reporter: Konstantin Shvachko
> Assignee: Owen O'Malley
> Priority: Minor
>
> 1. Examining HADOOP-264 bug I realized that not all rpc server exceptions are actually returned to the client. Particularly, if an exception happens in
> org.apache.hadoop.ipc.Server.Connection.run()
> for example inside
> param.readFields(in);
> then it logged but never returned back to the client.
> Client simply timeouts in this case, which is not exactly what one would expect.
> 2. On the way back
> org.apache.hadoop.ipc.Client.call()
> rpc client always throws a RemoteException, rather than the exception wrapped into this RemoteException.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.