Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52804

Jenkins web GUI hangs when using a computer with more then 70 CPU's

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      From version 2.117 jenkins web GUI hangs when using more then 70 cpus,  between 64 and 70 jenkins GUI is not updated correctly. Using wget instead of browser only to show what's failing, but using Chrome in real life

      Works fine (version 2.135 with 64 cpus)

      $docker run --cpuset-cpus=0-64 -p 8080:8080 -p 50000:50000 jenkins/jenkins:latest
      Running from: /usr/share/jenkins/jenkins.war
      webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")

      ....

      INFO: Jenkins is fully up and running
      --> setting agent port for jnlp
      --> setting agent port for jnlp... done

      $ wget localhost:8080
      -2018-07-30 22:52:42- http://localhost:8080/
      Resolving localhost (localhost)... ::1, 127.0.0.1
      Connecting to localhost (localhost)|::1|:8080... connected.
      HTTP request sent, awaiting response... 403 Forbidden
      2018-07-30 22:52:42 ERROR 403: Forbidden.

       

      Fails (Hangs forever in wget, version 2.135 with 70 cpus)

      $docker run --cpuset-cpus=0-70 -p 8080:8080 -p 50000:50000 jenkins/jenkins:latest
      Running from: /usr/share/jenkins/jenkins.war
      webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")

      ....

      INFO: Jenkins is fully up and running
      --> setting agent port for jnlp
      --> setting agent port for jnlp... done

      $ wget localhost:8080
      -2018-07-30 22:57:03- http://localhost:8080/
      Resolving localhost (localhost)... ::1, 127.0.0.1
      Connecting to localhost (localhost)|::(1|:8080... connected.
      HTTP request sent, awaiting response...

      Works fine (version 2.116 with 70 cpus)

      $docker run --cpuset-cpus=0-70 -p 8080:8080 -p 50000:50000 jenkins/jenkins:2.116
      Running from: /usr/share/jenkins/jenkins.war
      webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")

      ....

      INFO: Jenkins is fully up and running
      --> setting agent port for jnlp
      --> setting agent port for jnlp... done

      $ wget localhost:8080
      -2018-07-30 23:01:12- http://localhost:8080/
      Resolving localhost (localhost)... ::1, 127.0.0.1
      Connecting to localhost (localhost)|::1|:(8080... connected.
      HTTP request sent, awaiting response... 403 Forbidden
      2018-07-30 23:01:12 ERROR 403: Forbidden.

       

      Fails (Hangs forever in wget) (version 2.117 with 70 cpus)

      $docker run --cpuset-cpus=0-70 -p 8080:8080 -p 50000:50000 jenkins/jenkins:2.117 
      Running from: /usr/share/jenkins/jenkins.war
      webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")

      ....

      INFO: Jenkins is fully up and running
      --> setting agent port for jnlp
      --> setting agent port for jnlp... done

      $ wget localhost:8080
      -2018-07-30 23:06:14- http://localhost:8080/
      Resolving localhost (localhost)... ::1, 127.0.0.1
      Connecting to localhost (localhost)|::1|:8080... connected.
      HTTP request sent, awaiting response...

       Most likely it's a race condition issue in the updated related to the

      "Update Winstone from 4.1.2 to 4.2 to update Jetty from 9.4.5 to 9.4.8"

        Attachments

        1. docker_test64.out
          2.88 MB
        2. docker_test70.out
          2.87 MB
        3. docker64.log
          12 kB
        4. docker70.log
          6 kB
        5. jenkins.log.save
          3.31 MB
        6. jenkins.threaddump
          77 kB
        7. jstack.out
          0.2 kB
        8. jstack.out.F
          65 kB

          Issue Links

            Activity

            Hide
            olamy Olivier Lamy added a comment - - edited

            Eric Boehm

            or anyone having the issue can you please the war here  http://home.apache.org/~olamy/jenkins/

            use --help for other new jetty options

              

            Show
            olamy Olivier Lamy added a comment - - edited Eric Boehm or anyone having the issue can you please the war here  http://home.apache.org/~olamy/jenkins/ use --help for other new jetty options   
            Hide
            em_boehm Eric Boehm added a comment -

            Olivier,

            Yes, that does seem to fix the problems. I am able to connect with curl and the browser with all 72 processors enabled using http://home.apache.org/~olamy/jenkins/jenkins_winstone_pr_54.war

             

             

            Show
            em_boehm Eric Boehm added a comment - Olivier, Yes, that does seem to fix the problems. I am able to connect with curl and the browser with all 72 processors enabled using http://home.apache.org/~olamy/jenkins/jenkins_winstone_pr_54.war    
            Hide
            olamy Olivier Lamy added a comment -

            Good to hear feel free to vote/comment for JENKINS-53239 or https://github.com/jenkinsci/winstone/pull/54

            Show
            olamy Olivier Lamy added a comment - Good to hear feel free to vote/comment for  JENKINS-53239 or  https://github.com/jenkinsci/winstone/pull/54
            Show
            olamy Olivier Lamy added a comment - https://github.com/jenkinsci/winstone/commit/74775cc02ef92feaf247e45a32b193e45800805a
            Hide
            danielbeck Daniel Beck added a comment -

            Released on 2.141.

            Show
            danielbeck Daniel Beck added a comment - Released on 2.141.

              People

              • Assignee:
                olamy Olivier Lamy
                Reporter:
                wallinux Anders Wallin
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: