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

Lazy loading cause’s http links from other html pages into Jenkins do not work properly

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • Windows Server 2008 R2 - Apache Tomcat 7.0.2

      In our environment we have an overview page which contains several links into some workspaces and console output of Jenkins jobs. Since the lazy loading feature is introduced the links do not work properly any more. Maybe it’s possible to make the Feature optional …

      Thanks,
      Christian

          [JENKINS-15560] Lazy loading cause’s http links from other html pages into Jenkins do not work properly

          Jason Swager added a comment -

          Our Jenkins installation (1.496, Win2008R2) is having the same problems. A month ago, it was sporadic - once every 1000 builds or so. But we just finished adding a couple hundred more jobs and the problem got immediately worse. It's not just URLs to builds that is affected - other components also break for the same reason I suspect. The Copy Artifact plugin seems to have a similar problem. It will cause a build failure because it can't download artifacts from a specific build. This will happen repeatedly until someone uses a browser, goes to the job and specifically loads the problematic build. Once the build is display, the job can be run successfully.

          Jason Swager added a comment - Our Jenkins installation (1.496, Win2008R2) is having the same problems. A month ago, it was sporadic - once every 1000 builds or so. But we just finished adding a couple hundred more jobs and the problem got immediately worse. It's not just URLs to builds that is affected - other components also break for the same reason I suspect. The Copy Artifact plugin seems to have a similar problem. It will cause a build failure because it can't download artifacts from a specific build. This will happen repeatedly until someone uses a browser, goes to the job and specifically loads the problematic build. Once the build is display, the job can be run successfully.

          Jason Swager added a comment -

          Due to the nature of this bug, I'm bumping the issue up to Critical. It affects not only core Jenkins functionality, but also the behavior of some plugins.

          Jason Swager added a comment - Due to the nature of this bug, I'm bumping the issue up to Critical. It affects not only core Jenkins functionality, but also the behavior of some plugins.

          Jesse Glick added a comment -

          Any known way to reproduce?

          Jesse Glick added a comment - Any known way to reproduce?

          Jason Swager added a comment -

          I'm not sure of any easy way to reproduce. A temporary solution seems to be rebooting Jenkins.

          The way that I would try to reproduce is to load Jenkins with lots of jobs and lots of builds for each job. I'm guessing that if the memory used by the job/build objects is very high in regards to the available memory (sorry - don't know how to define "high"), the problem might occur. Having the jobs limit their number of archived builds, then running many times beyond that so that archived builds are being deleted might help cause the problem; I'm guessing this because a reboot temporarily fixes our problem. And although we keep 20 to 50 builds archived on each job, we have a high enough turn over that in two weeks, all builds are replaced - and the problem seems to happen the longer we run...

          Sorry for the vague and imprecise descriptions. When the problem occurs, we usually go into panic mode because Jenkins begins to fail in a variety of ways and we don't have a lot of time before we get flooded with calls from managers/engineers complaining about false build/test failure notifications, busted dashboards, etc.

          Jason Swager added a comment - I'm not sure of any easy way to reproduce. A temporary solution seems to be rebooting Jenkins. The way that I would try to reproduce is to load Jenkins with lots of jobs and lots of builds for each job. I'm guessing that if the memory used by the job/build objects is very high in regards to the available memory (sorry - don't know how to define "high"), the problem might occur. Having the jobs limit their number of archived builds, then running many times beyond that so that archived builds are being deleted might help cause the problem; I'm guessing this because a reboot temporarily fixes our problem. And although we keep 20 to 50 builds archived on each job, we have a high enough turn over that in two weeks, all builds are replaced - and the problem seems to happen the longer we run... Sorry for the vague and imprecise descriptions. When the problem occurs, we usually go into panic mode because Jenkins begins to fail in a variety of ways and we don't have a lot of time before we get flooded with calls from managers/engineers complaining about false build/test failure notifications, busted dashboards, etc.

          So what exactly happens when you say those links don't work? 404? Something else?

          Kohsuke Kawaguchi added a comment - So what exactly happens when you say those links don't work? 404? Something else?

          Jason Swager added a comment -

          404 error code is the result.

          Jason Swager added a comment - 404 error code is the result.

          Here is what happens at our Jenkins: If we try to access e.g. a console output using the complete URL (pasting the URL to a browser, not navigating to the console output via the Jenkins page) the 404 error occurs. If we once navigate to the build via Jenkins, pasting the complete URL to a browser works again.

          Christian Grobauer added a comment - Here is what happens at our Jenkins: If we try to access e.g. a console output using the complete URL (pasting the URL to a browser, not navigating to the console output via the Jenkins page) the 404 error occurs. If we once navigate to the build via Jenkins, pasting the complete URL to a browser works again.

          Does the server console report any errors/warnings?

          I'm afraid as it stands now, this ticket is too vague to let us act on it.

          Kohsuke Kawaguchi added a comment - Does the server console report any errors/warnings? I'm afraid as it stands now, this ticket is too vague to let us act on it.

          Based on the comment from Chirstian that his Jenkins is on Windows 2008 and he can get Jenkins to load the build if he tries to access it through certain means, I'm marking this ticket as DUPLICATE of JENKINS-15589 (which in turn is caused by JENKINS-15587).

          The fix is committed toward 1.507.

          Kohsuke Kawaguchi added a comment - Based on the comment from Chirstian that his Jenkins is on Windows 2008 and he can get Jenkins to load the build if he tries to access it through certain means, I'm marking this ticket as DUPLICATE of JENKINS-15589 (which in turn is caused by JENKINS-15587 ). The fix is committed toward 1.507.

            kohsuke Kohsuke Kawaguchi
            cgrb Christian Grobauer
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: