Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 4 Jan 2013 03:30:12 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12625408.1356686566919.78225.1357270212904@arcas>
In-Reply-To: <JIRA.12625408.1356686566919@arcas>
References: <JIRA.12625408.1356686566919@arcas>
Subject: [jira] [Commented] (HBASE-7450) orphan RPC connection in
 HBaseClient leaves "null" out member, causing NPE in HCM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-7450?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1354=
3571#comment-13543571 ]=20

Hadoop QA commented on HBASE-7450:
----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest=
 attachment=20
  http://issues.apache.org/jira/secure/attachment/12563220/7450_v3.txt
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author=
 tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 =
new or modified tests.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoo=
p 2.0 profile.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any =
warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the =
total number of javac compiler warnings.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new =
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not incre=
ase the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines=
 longer than 100

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3846//tes=
tReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.=
html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.=
html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3846=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.h=
tml
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3846//c=
onsole

This message is automatically generated.
               =20
> orphan RPC connection in HBaseClient leaves "null" out member, causing NP=
E in HCM
> -------------------------------------------------------------------------=
--------
>
>                 Key: HBASE-7450
>                 URL: https://issues.apache.org/jira/browse/HBASE-7450
>             Project: HBase
>          Issue Type: Bug
>          Components: IPC/RPC
>    Affects Versions: 0.92.0
>            Reporter: Zavier Gao
>            Assignee: Zavier Gao
>             Fix For: 0.96.0
>
>         Attachments: 7450_v1.txt, 7450_v2.txt, 7450_v3.txt
>
>
> Just like:=E3=80=80https://issues.apache.org/jira/browse/HADOOP-7428
> Exceptions except IOException thrown in setupIOstreams would leave the co=
nnection half-setup. But the connection would not close utill it become tim=
eout. The orphane connection cause NPE when is used in HCM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira