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

NullPointerException at startup -- SEVERE: Timer task hudson.WebAppMain failed

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • Linux

      I'm seeing the following exception thrown at startup...

      Oct 21, 2010 9:37:00 AM hudson.triggers.SafeTimerTask run
      SEVERE: Timer task hudson.WebAppMain$2$1@109037d failed
      java.lang.NullPointerException
      at java.lang.String.startsWith(String.java:1421)
      at java.lang.String.startsWith(String.java:1450)
      at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:178)
      at hudson.maven.MavenModuleSetBuild$1.<init>(MavenModuleSetBuild.java:147)
      at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:141)
      at hudson.maven.FilteredChangeLogSet.<init>(FilteredChangeLogSet.java:51)
      at hudson.maven.MavenBuild.getChangeSet(MavenBuild.java:161)
      at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:315)
      at hudson.model.User.getBuilds(User.java:369)
      at hudson.WebAppMain$2$1.doRun(WebAppMain.java:227)
      at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
      at java.util.TimerThread.mainLoop(Timer.java:512)
      at java.util.TimerThread.run(Timer.java:462)

      I believe the problem began showing up in version 1.378.

      I am currently using:
      Hudson - 1.381
      Static Analysis Collector Plug-in - 1.8
      Static Analysis Utilities - 1.14
      Hudson Backup plugin - 1.5
      Checkstyle Plug-in - 3.10
      Hudson CVS Plug-in - 1.2
      Hudson Dependency Analyzer Plugin - 0.5
      Hudson Email Extension Plugin - 2.9
      FindBugs Plug-in - 4.14
      Hudson Maven Release Plug-in Plug-in - 0.6.1
      Hudson Maven Info Plugin - 0.0.3
      Maven Integration plugin - 1.381
      PMD Plug-in - 3.10
      Hudson Support Subscription Notification Plugin - 1.2
      Hudson SSH Slaves plugin - 0.13
      Hudson Subversion Plug-in - 1.17
      Warnings Plug-in - 3.11

      I'm not sure whether this is causing any real problems, but after I first saw it I was having problems with build hanging, and I was forced to revert to an earlier version of Hudson. If this exception isn't important, I'd like to see it cleaned up. If it is indicative of a larger problems, can we get a fix?

          [JENKINS-7870] NullPointerException at startup -- SEVERE: Timer task hudson.WebAppMain failed

          sinkha added a comment -

          Immediately after submitting this bug, I started to see builds failing, so it definitely needs to be fixed.

          ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net
          java.lang.NullPointerException
          at java.lang.String.startsWith(String.java:1421)
          at java.lang.String.startsWith(String.java:1450)
          at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:178)
          at hudson.maven.MavenModuleSetBuild$1.<init>(MavenModuleSetBuild.java:147)
          at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:141)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:423)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
          at hudson.model.Run.run(Run.java:1280)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:139)

          sinkha added a comment - Immediately after submitting this bug, I started to see builds failing, so it definitely needs to be fixed. ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net java.lang.NullPointerException at java.lang.String.startsWith(String.java:1421) at java.lang.String.startsWith(String.java:1450) at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:178) at hudson.maven.MavenModuleSetBuild$1.<init>(MavenModuleSetBuild.java:147) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:141) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:423) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416) at hudson.model.Run.run(Run.java:1280) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:139)

          km added a comment -

          Some context is needed. It appears that it's a Maven2 Job whose build is failing. There was one change in this area in the source code, but I am certain that is not why this NullPointerException is thrown.

          km added a comment - Some context is needed. It appears that it's a Maven2 Job whose build is failing. There was one change in this area in the source code, but I am certain that is not why this NullPointerException is thrown.

          Think is same problem as in JENKINS-7854

          rainerweinhold added a comment - Think is same problem as in JENKINS-7854

          sinkha added a comment -

          I agree, it looks like it could be the same issue. I think rainerweinhold might be on the right track...on JENKINS-7854 he commented that the bug may have been introduced by the fix provided for JENKINS-5357. The timing fits with when I started seeing the issue and I believe the problem was cropping up in sub-module builds.

          I'll try to provide some more detailed output if I can, but I only have our production Hudson server which I already reverted to 1.377. We have a lot of deadlines this month, so it's not a good time for me to be playing around with our setup. If I can, I'll try to upgrade again to reproduce the problem soon, and then attach more detailed logs. Hopefully rainerweinhold can provide enough info that I won't need to.

          sinkha added a comment - I agree, it looks like it could be the same issue. I think rainerweinhold might be on the right track...on JENKINS-7854 he commented that the bug may have been introduced by the fix provided for JENKINS-5357 . The timing fits with when I started seeing the issue and I believe the problem was cropping up in sub-module builds. I'll try to provide some more detailed output if I can, but I only have our production Hudson server which I already reverted to 1.377. We have a lot of deadlines this month, so it's not a good time for me to be playing around with our setup. If I can, I'll try to upgrade again to reproduce the problem soon, and then attach more detailed logs. Hopefully rainerweinhold can provide enough info that I won't need to.

          kutzi added a comment -

          Please watch and comment on JENKINS-7684

          kutzi added a comment - Please watch and comment on JENKINS-7684

            Unassigned Unassigned
            sinkha sinkha
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: