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

ROADMAP: Improve Start-up Time

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • core
    • None

    Description

      Attachments

        Issue Links

          Activity

            jburrows John Burrows added a comment -

            Build records are not getting loaded at all, even after the Jenkins service has been up for more than 18 hours. If there is some step needed to get back the build records or get them loaded, it should have been represented in the Changelog.
            Please fix this issue.
            Log entries show:

            I looked at the 'jenkins.err' on the Jenkins server & saw errors similar to these:

            Oct 12, 2012 2:06:01 AM org.kohsuke.stapler.compression.CompressionFilter reportException
            WARNING: Untrapped servlet exception
            javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/hudson/model/View/index.jelly:44:43: <st:include> org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/hudson/projectView.jelly:60:22: <d:invokeBody> org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/layout/tab.jelly:46:18: <j:otherwise> Failed to write to client
            at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
            at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
            at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
            at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
            at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625)
            at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
            at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
            at org.kohsuke.stapler.Stapler.service(Stapler.java:162)

            Oct 12, 2012 2:11:01 AM hudson.model.Run execute
            INFO: DBS_RETAIL_R5-SNAPSHOT #102 main build action completed: SUCCESS
            Oct 12, 2012 2:11:01 AM hudson.model.Executor run
            SEVERE: Executor threw an exception
            java.lang.NullPointerException
            at hudson.tasks.LogRotator.perform(LogRotator.java:119)
            at hudson.model.Job.logRotate(Job.java:338)
            at hudson.model.Run.execute(Run.java:1581)
            at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
            at hudson.model.ResourceController.execute(ResourceController.java:88)
            at hudson.model.Executor.run(Executor.java:236)

            jburrows John Burrows added a comment - Build records are not getting loaded at all, even after the Jenkins service has been up for more than 18 hours. If there is some step needed to get back the build records or get them loaded, it should have been represented in the Changelog. Please fix this issue. Log entries show: I looked at the 'jenkins.err' on the Jenkins server & saw errors similar to these: Oct 12, 2012 2:06:01 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/hudson/model/View/index.jelly:44:43: <st:include> org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/hudson/projectView.jelly:60:22: <d:invokeBody> org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/layout/tab.jelly:46:18: <j:otherwise> Failed to write to client at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) Oct 12, 2012 2:11:01 AM hudson.model.Run execute INFO: DBS_RETAIL_R5-SNAPSHOT #102 main build action completed: SUCCESS Oct 12, 2012 2:11:01 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.tasks.LogRotator.perform(LogRotator.java:119) at hudson.model.Job.logRotate(Job.java:338) at hudson.model.Run.execute(Run.java:1581) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)

            There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439. I'm pretty sure that those are the issues that you are seeing.

            Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from
            https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/

            oldelvet Richard Mortimer added a comment - There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439 . I'm pretty sure that those are the issues that you are seeing. Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/
            jburrows John Burrows added a comment -

            More info, after each restart of Jenkins, it clears out any and all build history again.

            jburrows John Burrows added a comment - More info, after each restart of Jenkins, it clears out any and all build history again.
            jburrows John Burrows added a comment -

            Looks like the issue was re-opened as another issue:
            See JENKINS-15465 and JENKINS-15439

            jburrows John Burrows added a comment - Looks like the issue was re-opened as another issue: See JENKINS-15465 and JENKINS-15439

            Looks like this feature breaks a lot. See https://issues.jenkins-ci.org/browse/JENKINS-15156
            Would be nice to have a patch that reverts the change.

            nickolay_martinov Nikolay Martynov added a comment - Looks like this feature breaks a lot. See https://issues.jenkins-ci.org/browse/JENKINS-15156 Would be nice to have a patch that reverts the change.

            People

              kohsuke Kohsuke Kawaguchi
              jieryn jieryn
              Votes:
              39 Vote for this issue
              Watchers:
              35 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: