You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Liang Xie (JIRA)" <ji...@apache.org> on 2014/12/22 08:11:13 UTC

[jira] [Created] (HADOOP-11439) TestWebDelegationToken is flaky

Liang Xie created HADOOP-11439:
----------------------------------

             Summary: 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)