[
https://issues.apache.org/jira/browse/HADOOP-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041930#comment-13041930
]
Hadoop QA commented on HADOOP-7121:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12481024/hadoop-7121.txt
against trunk revision 1129905.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/551//testReport/
Findbugs warnings:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/551//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/551//console
This message is automatically generated.
> Exceptions while serializing IPC call response are not handled well
> -------------------------------------------------------------------
>
> Key: HADOOP-7121
> URL: https://issues.apache.org/jira/browse/HADOOP-7121
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Labels: newbie
> Fix For: 0.22.0
>
> Attachments: hadoop-7121.txt, hadoop-7121.txt
>
>
> We had a situation where for some reason the serialization of an RPC call's
> response was throwing OOME. When this happens, the exception is not caught,
> and the call never gets a response - the client just hangs. Additionally, the
> OOME propagated all the way to the top of the IPC handler and caused the
> handler. Plus, the Handler upon exit only logged to stdout and not to the
> log4j logs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
