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

NPE while loading job config

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After updating to 1.559 one of my Maven jobs doesn't show up in the job listing.

      SEVERE: Failed Loading job <xxxx>
      java.lang.NullPointerException
      at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:784)
      at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:782)
      at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:115)
      at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:782)
      at hudson.model.Items.load(Items.java:278)
      at jenkins.model.Jenkins$18.run(Jenkins.java:2592)
      at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
      at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
      at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
      at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
      at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:744)

        Attachments

          Activity

          Hide
          chrislovsund Christian Lövsund added a comment - - edited

          I got the same error, my workaround was to remove modules folder.
          Did this because of the WARNING in:

          jenkins.log

          WARNING: could not find file /var/lib/jenkins/jobs/ds-integration-tests/modules/ifs.dev$ReportAnnotationsAsPMD/config.xml
          Apr 17, 2014 11:18:30 AM jenkins.InitReactorRunner$1 onTaskFailed
          SEVERE: Failed Loading job ds-integration-tests
          java.lang.NullPointerException
          at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:784)
          at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:782)
          at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:115)
          at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:782)
          at hudson.model.Items.load(Items.java:278)
          at jenkins.model.Jenkins$18.run(Jenkins.java:2592)
          at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
          at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
          at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
          at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
          at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
          at java.lang.Thread.run(Thread.java:724)

          Show
          chrislovsund Christian Lövsund added a comment - - edited I got the same error, my workaround was to remove modules folder. Did this because of the WARNING in: jenkins.log WARNING: could not find file /var/lib/jenkins/jobs/ds-integration-tests/modules/ifs.dev$ReportAnnotationsAsPMD/config.xml Apr 17, 2014 11:18:30 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job ds-integration-tests java.lang.NullPointerException at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:784) at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:782) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:115) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:782) at hudson.model.Items.load(Items.java:278) at jenkins.model.Jenkins$18.run(Jenkins.java:2592) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724)
          Hide
          larsmartin Lars Martin added a comment -

          Hi Christian, thanks for the hint. Obviously I ignored the prior warning. Removing the 'modules' folder worked for me too.

          Show
          larsmartin Lars Martin added a comment - Hi Christian, thanks for the hint. Obviously I ignored the prior warning. Removing the 'modules' folder worked for me too.
          Show
          olamy Olivier Lamy added a comment - should be fixed https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
          Hide
          abayer Andrew Bayer added a comment -

          So interestingly, I just got rid of the underlying problem - we still saw slow startup times with or without olamy's commit, but once I found every module directory without a config.xml in it and blew it away, our startup time at builds.apache.org went from 25-30 minutes to 4. Now admittedly, there's a bunch of nasty i/o things going on there from running on zfs on linux, but still, there's a real issue here, IMO, in terms of traversing modules that aren't really valid every time instead of doing something about 'em.

          Show
          abayer Andrew Bayer added a comment - So interestingly, I just got rid of the underlying problem - we still saw slow startup times with or without olamy's commit, but once I found every module directory without a config.xml in it and blew it away, our startup time at builds.apache.org went from 25-30 minutes to 4. Now admittedly, there's a bunch of nasty i/o things going on there from running on zfs on linux, but still, there's a real issue here, IMO, in terms of traversing modules that aren't really valid every time instead of doing something about 'em.
          Hide
          jglick Jesse Glick added a comment -

          @abayer not really sure what your comment is about, but sounds like a separate bug; this one is fixed AFAICT.

          Show
          jglick Jesse Glick added a comment - @abayer not really sure what your comment is about, but sounds like a separate bug; this one is fixed AFAICT.

            People

            • Assignee:
              olamy Olivier Lamy
              Reporter:
              larsmartin Lars Martin
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: