Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <14853724.841274225218120.JavaMail.jira@thor>
Date: Tue, 18 May 2010 19:26:58 -0400 (EDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-6760) WebServer shouldn't increase port
 number in case of negative port setting caused by Jetty's race
In-Reply-To: <17436829.8001273601621435.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Boudnik updated HADOOP-6760:
---------------------------------------

    Status: Patch Available  (was: Open)

Patch is the same except for CHANGES.txt mods. Re verifying nonetheless. 

> WebServer shouldn't increase port number in case of negative port setting caused by Jetty's race
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6760
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6760
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.3
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-6760.0.20.patch, HADOOP-6760.0.20.patch, HADOOP-6760.0.20.patch, HADOOP-6760.patch, HADOOP-6760.patch, HADOOP-6760.patch
>
>
> When a negative port is assigned to a webserver socket (because of a race inside of the Jetty server) the workaround from HADOOP-6386 is increasing the original port number on the next bind attempt. Apparently, this is an incorrect logic and next bind attempt should happen on the same port number if possible.

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