[
https://issues.apache.org/jira/browse/HADOOP-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-1561:
---------------------------------
Description:
RPC server logs and sends the exceptions that occur inside the call. But if
there is an exception during construction of objects, the exception is not
logged. Clients just see EOF because server closes the connection.
I got bitten by this since couple of my objects did not have default
constructors (and same case if readFields() throws an NPE). This is a silly
mistake on my part but I think it is easy to make the mistake but hard to see
where the problem is.
Server can still close the connection but should log it at the server.
was:
RPC server logs and sends the exceptions that occur inside the call. But if
there is an exception during construction of objects, the exception is not
logged. Clients just see EOF because server closes the connection.
I got bitten by this since couple of my objects did not have default
constructors (and same case if readFields() throws an NPE). This is a silly
mistake on part but I think it is easy to make the mistake but hard to where
the problem is.
Server can still close the connection but should log it at the server.
> RPC server should log exceptions that are not sent to client.
> -------------------------------------------------------------
>
> Key: HADOOP-1561
> URL: https://issues.apache.org/jira/browse/HADOOP-1561
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Reporter: Raghu Angadi
> Priority: Minor
> Fix For: 0.14.0
>
>
> RPC server logs and sends the exceptions that occur inside the call. But if
> there is an exception during construction of objects, the exception is not
> logged. Clients just see EOF because server closes the connection.
> I got bitten by this since couple of my objects did not have default
> constructors (and same case if readFields() throws an NPE). This is a silly
> mistake on my part but I think it is easy to make the mistake but hard to see
> where the problem is.
> Server can still close the connection but should log it at the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
