Varun Saxena commented on YARN-2912:

[~ste...@apache.org], well opening up of a socket on the port is done by 
Jersey. Port being occupied by another process running on the same machine is 
also a possibility.
So, I have simply added code for rolling increment of ports for Jersey tests. 
Increment is by 10 to ensure that if the port is occupied because another 
application is using it, it will mitigate the risk of next port being occupied 
if the application uses multiple ports

> 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

Reply via email to