[
https://issues.apache.org/jira/browse/HADOOP-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867330#action_12867330
]
Eli Collins commented on HADOOP-6760:
-------------------------------------
Yes, I was just simplying the HADOOP-4744 part, looks like you could do
something similar for the HADOOP-6386 part. Feel free to ignore or defer to a
separate jira, at the minimum that code could use a big comment explaining why
it's jumping through so many hoops.
+1 to your patch. The change for HADOOP-6386 should not have incremented
oriPort.
> 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.
