hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (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 Tue, 11 May 2010 18:35:46 GMT

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

Hadoop QA commented on HADOOP-6760:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12444225/HADOOP-6760.0.20.patch
  against trunk revision 941662.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/515/console

This message is automatically generated.

> 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