[
https://issues.apache.org/jira/browse/HADOOP-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860785#action_12860785
]
Hadoop QA commented on HADOOP-6724:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442801/hadoop-6724.txt
against trunk revision 937881.
+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 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 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/479/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/479/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/479/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/479/console
This message is automatically generated.
> IPC doesn't properly handle IOEs thrown by socket factory
> ---------------------------------------------------------
>
> Key: HADOOP-6724
> URL: https://issues.apache.org/jira/browse/HADOOP-6724
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.20.3, 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hadoop-6724.txt
>
>
> If the socket factory throws an IOE inside setupIOStreams, then
> handleConnectionFailure will be called with socket still null, and thus
> generate an NPE on socket.close(). This ends up orphaning clients, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
