• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      ERROR: Processing failed due to a bug in the code. Please report this to
      users@hudson.dev.java.net

      java.lang.NullPointerException

      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:381)

      at hudson.model.Run.run(Run.java:1174)

      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303)

      at hudson.model.ResourceController.execute(ResourceController.java:88)

      at hudson.model.Executor.run(Executor.java:123)

      project=hudson.maven.MavenModuleSet@b2db5b[accommons-libs]

      project.getModules()=[hudson.maven.MavenModule@38fb59[accommons-libs/com.accor.commons:accommons-libs-root],
      hudson.maven.MavenModule@fdb413[accommons-libs/com.accor.commons:split-tars],
      hudson.maven.MavenModule@396fce[accommons-libs/com.accor.commons.cache:accommons-cache],
      hudson.maven.MavenModule@db5b3f[accommons-libs/com.accor.commons.configuration:plexus-configuration],
      hudson.maven.MavenModule@1438dbe[accommons-libs/com.accor.commons.configuration:plexus-configuration-api],
      hudson.maven.MavenModule@ece36[accommons-libs/com.accor.commons.configuration:plexus-configuration-jdbc],
      hudson.maven.MavenModule@46136[accommons-libs/com.accor.commons.configuration:plexus-configuration-prefs],
      hudson.maven.MavenModule@18a2977[accommons-libs/com.accor.commons.plexus:accommons-plexus-utils],
      hudson.maven.MavenModule@1a8739b[accommons-libs/com.accor.commons.plexus.components:accommons-plexus-components],
      hudson.maven.MavenModule@3dd246[accommons-libs/com.accor.commons.plexus.components:jdbc-connection-pool],
      hudson.maven.MavenModule@b7f2d0[accommons-libs/com.accor.commons.plexus.components:stored-procedure-parser],
      hudson.maven.MavenModule@a64a92[accommons-libs/com.accor.commons.prefs:accommons-prefs],
      hudson.maven.MavenModule@169da74[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor],
      hudson.maven.MavenModule@84f665[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor-api],
      hudson.maven.MavenModule@14c8822[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor-model],
      hudson.maven.MavenModule@17d8769[accommons-libs/com.accor.commons.tools:accommons-tools],
      hudson.maven.MavenModule@453dd5[accommons-libs/com.accor.commons.tools:jersey-apache-client],
      hudson.maven.MavenModule@1dea382[accommons-libs/com.accor.commons.transporter:file-transporters],
      hudson.maven.MavenModule@1c0adca[accommons-libs/com.accor.commons.xmlschemas:schemas-validator],
      hudson.maven.MavenModule@d1afd3[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-api],
      hudson.maven.MavenModule@6e795b[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-jaxp],
      hudson.maven.MavenModule@e1469c[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-msv],
      hudson.maven.MavenModule@1e2bda7[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-xerces],
      hudson.maven.MavenModule@1115a61[accommons-libs/com.accor.components.cache:spring-cache],
      hudson.maven.MavenModule@44ac5e[accommons-libs/com.accor.components.cache:spring-cache-api],
      hudson.maven.MavenModule@904f75[accommons-libs/com.accor.components.cache:spring-cache-ehcache],
      hudson.maven.MavenModule@5098f9[accommons-libs/com.accor.components.cache:spring-cache-hashmap],
      hudson.maven.MavenModule@16b277f[accommons-libs/com.accor.components.cache:spring-cache-oscache],
      hudson.maven.MavenModule@1ee2ea8[accommons-libs/com.accor.components.cache:spring-cache-providers],
      hudson.maven.MavenModule@394ffa[accommons-libs/com.accor.components.cache:spring-cache-test],
      hudson.maven.MavenModule@b1bed2[accommons-libs/com.accor.components.cache:spring-cache-whirlycache],
      hudson.maven.MavenModule@166ce5f[accommons-libs/com.accor.hudson.plugins:hudson-plugins],
      hudson.maven.MavenModule@76f1f4[accommons-libs/com.accor.hudson.plugins:mavenrelease],
      hudson.maven.MavenModule@10704e1[accommons-libs/commons-logging:commons-logging], hudson.maven.MavenModule@1d18084[accommons-libs/commons-logging:commons-logging-api],
      hudson.maven.MavenModule@14c7deb[accommons-libs/commons-logging:commons-logging-parent]]

      project.getRootModule()=hudson.maven.MavenModule@38fb59[accommons-libs/com.accor.commons:accommons-libs-root]

      FATAL: null

      java.lang.NullPointerException

      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:381)

      at hudson.model.Run.run(Run.java:1174)

      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303)

      at hudson.model.ResourceController.execute(ResourceController.java:88)

      at hudson.model.Executor.run(Executor.java:123)

          [JENKINS-4788] NPE on maven build with 1.331

          Olivier Lamy added a comment -

          doesn't failed with "Incremental Build" not activated.

          Olivier Lamy added a comment - doesn't failed with "Incremental Build" not activated.

          Andrew Bayer added a comment -

          Does this happen every time you build without incremental build turned on, or
          only sometimes?

          Andrew Bayer added a comment - Does this happen every time you build without incremental build turned on, or only sometimes?

          Olivier Lamy added a comment -

          in fact only since today

          Olivier Lamy added a comment - in fact only since today

          Andrew Bayer added a comment -

          Hrm. I'm not able to reproduce this so far. If you run a build with incremental
          build turned off, and then turn incremental build back on, does this NPE still
          show up?

          Andrew Bayer added a comment - Hrm. I'm not able to reproduce this so far. If you run a build with incremental build turned off, and then turn incremental build back on, does this NPE still show up?

          Olivier Lamy added a comment -

          no not more.but weird

          Olivier Lamy added a comment - no not more.but weird

          Andrew Bayer added a comment -

          I'm guessing this is a sign that my earlier fix for the NPE that showed up when
          a new module was added isn't working quite right - I'll try some more
          permutations in order to reproduce this.

          Andrew Bayer added a comment - I'm guessing this is a sign that my earlier fix for the NPE that showed up when a new module was added isn't working quite right - I'll try some more permutations in order to reproduce this.

          Andrew Bayer added a comment -

          Yeah, I've still seen some seemingly random incidents of this NPE showing up with incremental build on, at least through 1.335 or so, but I can't reproduce them on my 1.348 test instance. If you see this show up again, let me know.

          Andrew Bayer added a comment - Yeah, I've still seen some seemingly random incidents of this NPE showing up with incremental build on, at least through 1.335 or so, but I can't reproduce them on my 1.348 test instance. If you see this show up again, let me know.

          bjansen added a comment -

          I have the same issue. Sometimes.

          It seems to appear when the previous build has failed.

          Today our hudson slave was reset while a build was running. That caused exception:
          java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid object ID 22
          at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:268)
          at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:255)

          After that every new build gives the NPE as described above.
          The workaround to disable incremental build is working. When I enable incremental build again, all works fine again

          We are running hudson version 1.342

          bjansen added a comment - I have the same issue. Sometimes. It seems to appear when the previous build has failed. Today our hudson slave was reset while a build was running. That caused exception: java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid object ID 22 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:268) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:255) After that every new build gives the NPE as described above. The workaround to disable incremental build is working. When I enable incremental build again, all works fine again We are running hudson version 1.342

          kutzi added a comment -

          Looks like a duplicate of JENKINS-6429.
          Can you confitm that this is fixed in current versions?

          kutzi added a comment - Looks like a duplicate of JENKINS-6429 . Can you confitm that this is fixed in current versions?

          Olivier Lamy added a comment -

          personnally no more issue here.

          Olivier Lamy added a comment - personnally no more issue here.

            Unassigned Unassigned
            olamy Olivier Lamy
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: