hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6760) WebServer shouldn't increase port number in case of negative port setting caused by Jetty's race
Date Fri, 14 May 2010 01:25:42 GMT

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

Devaraj Das commented on HADOOP-6760:
-------------------------------------

+1 on reverting HADOOP-6386 for now. BTW http://jira.codehaus.org/browse/JETTY-748 is the
jira that is tracking the fix on the jetty side.

> 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
>         Attachments: HADOOP-6760.0.20.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.


Mime
View raw message