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

Konstantin Boudnik commented on HADOOP-6386:
--------------------------------------------

You've brought up an interesting issue. According to the latest Jetty source 
code 
[Container.java|http://jetty.cvs.sourceforge.net/viewvc/jetty/Jetty/src/org/mortbay/util/Container.java?revision=1.5&view=markup]
 first calls polymorphic {{doStart()}} and then sets {{_started}} flag to 
{{true}}. I.e.
{noformat}
            doStart();
            _started=true;
{noformat}
Now, 
[HttpServer|http://jetty.cvs.sourceforge.net/viewvc/jetty/Jetty/src/org/mortbay/http/HttpServer.java?revision=1.70&view=markup]'s
 {{doStart()}} method JavaDoc states that 
{noformat}
    /** Start all handlers then listeners.
     * If a subcomponent fails to start, it's exception is added to a
     * org.mortbay.util.MultiException and the start method continues.
{noformat}

So, strictly speaking this isn't an asynchronous method. Besides, if something 
would go wrong we are likely to see an MultiException thrown by this 'failing' 
server instance. However, we don't see any. Which brings me to the conclusion 
that server seems to start properly and {{isStarted()}} is going to return 
{{true}} in this case. 

There's still a chance that we are dealing with a race condition in the Jetty 
server, but it isn't apparent what's causing it ;-(

> NameNode's HttpServer can't instantiate InetSocketAddress: 
> IllegalArgumentException is thrown
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6386
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6386
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>         Environment: Apache Hudson build machine
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>            Priority: Blocker
>         Attachments: HADOOP-6386-0.20.patch, HADOOP-6386.patch, 
> hdfs-771.patch, hdfs-771.patch, testEditLog.html
>
>
> In an execution of a tests the following exception has been thrown:
> {noformat}
> Error Message
> port out of range:-1
> Stacktrace
> java.lang.IllegalArgumentException: port out of range:-1
>       at java.net.InetSocketAddress.<init>(InetSocketAddress.java:118)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.java:371)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.activate(NameNode.java:313)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:304)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:410)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:404)
>       at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1211)
>       at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:287)
>       at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:131)
>       at 
> org.apache.hadoop.hdfs.server.namenode.TestEditLog.testEditLog(TestEditLog.java:92)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to