[ 
https://issues.apache.org/jira/browse/HADOOP-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056670#comment-13056670
 ] 

Hadoop QA commented on HADOOP-7428:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12484478/hadoop-7428.txt
  against trunk revision 1140442.

    +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/job/PreCommit-HADOOP-Build/681//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/681//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/681//console

This message is automatically generated.

> IPC connection is orphaned with null 'out' member
> -------------------------------------------------
>
>                 Key: HADOOP-7428
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7428
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-7428.txt
>
>
> We had a situation a JT ended up in a state where a certain user could not 
> submit a job, due to an NPE on the following line in {{sendParam}}:
> {code}
> synchronized (Connection.this.out) {
> {code}
> Looking at the code, my guess is that an RTE was thrown in setupIOstreams, 
> which only catches IOE. This could leave the connection in a half-setup state 
> which is never cleaned up and also cannot perform IPCs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to