Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 21 Jun 2012 11:56:43 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <819063840.38556.1340279803222.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <107253994.35916.1340225022436.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6248) Jetty init may fail if directory
 name contains "master"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-6248:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #62 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/62/])
    HBASE-6248 Jetty init may fail if directory name contains "master" (Dave Revell) (Revision 1352395)

     Result = FAILURE
tedyu : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/InfoServer.java

                
> Jetty init may fail if directory name contains "master"
> -------------------------------------------------------
>
>                 Key: HBASE-6248
>                 URL: https://issues.apache.org/jira/browse/HBASE-6248
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.94.0
>            Reporter: Dave Revell
>            Assignee: Dave Revell
>            Priority: Minor
>             Fix For: 0.96.0, 0.94.1
>
>         Attachments: HBASE-6248-0.94.0-0.diff, HBASE-6248-0.94.0-1.diff
>
>
> InfoServer.getWebAppsPath() unsafely assumes that any instance of the string "master" in the full path to hbase-webapps can be truncated. This breaks in the case where hbase is installed in a directory such as "/my/hbasemaster/".
> The result is that Jetty initialization will fail since the master determines an incorrect path to hbase-webapps. The master still runs but the web UI returns 503.
> I have a patch for this problem that I'll upload soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira