[ 
https://issues.apache.org/jira/browse/YARN-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237485#comment-14237485
 ] 

Varun Saxena commented on YARN-2912:
------------------------------------

[~rohithsharma], yes I tried setting system property as 0 but that did not 
work. As socket invocation is done by Jersey API we cant do much other than 
setting a custom port. The increment of 10 is because if processes open 
multiple ports they generally do it in a sequence and hence increment by 1 may 
also lead to port being occupied. Incrementing by 10 will mitigate this risk 

> Jersey Tests failing with port in use
> -------------------------------------
>
>                 Key: YARN-2912
>                 URL: https://issues.apache.org/jira/browse/YARN-2912
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0
>         Environment: jenkins on java 8
>            Reporter: Steve Loughran
>            Assignee: Varun Saxena
>             Fix For: 2.7.0
>
>         Attachments: YARN-2912.patch
>
>
> Jersey tests like TestNMWebServices apps are failing with port in use.
> The jersey test runner appears to always use the same port unless a system 
> property is set to point to a different one. Every test should really be 
> changing that sysprop in a @Before method



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to