[
https://issues.apache.org/jira/browse/HADOOP-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen resolved HADOOP-11439.
--------------------------------
Resolution: Duplicate
I believe this has been fixed by HADOOP-12417, resolving as dup. Thanks
[~xieliang007] for reporting.
> TestWebDelegationToken is flaky
> -------------------------------
>
> Key: HADOOP-11439
> URL: https://issues.apache.org/jira/browse/HADOOP-11439
> Project: Hadoop Common
> Issue Type: Test
> Components: security, test
> Affects Versions: 2.7.0
> Reporter: Liang Xie
> Assignee: Liang Xie
>
> see
> https://builds.apache.org/job/PreCommit-HDFS-Build/9101//testReport/org.apache.hadoop.security.token.delegation.web/TestWebDelegationToken/testDelegationTokenAuthenticatorCallsWithQueryString/
> through we have set the port to 0 in
> {code}
> protected Server createJettyServer() {
> try {
> InetAddress localhost = InetAddress.getLocalHost();
> ServerSocket ss = new ServerSocket(0, 50, localhost);
> int port = ss.getLocalPort();
> ss.close();
> jetty = new Server(0);
> jetty.getConnectors()[0].setHost("localhost");
> jetty.getConnectors()[0].setPort(port);
> {code}
> but in a QA robot env, it still could see the new random port be grab by
> other testing case or third party applicatons just between "ss.close" and
> "jetty.start()" call. so we still need a BindException retry here probably.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
