Repository navigation
[JENKINS-11458] NPE running Maven 3 job #16182
Description
Getting this at the start of the build. Its reporting FAILURE building the parent module (aggregated poms) this is after upgrading from Jenkins 1.432 to 1.436. Reverting back to 1.432 problem goes away.
Config is a M3 project I've tried 1 or more threads with same result.
15:04:36 mavenExecutionResult exceptions not empty
15:04:36 message : Internal error: java.lang.NullPointerException
15:04:36 cause : null
15:04:36 Stack trace :
15:04:36 org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
15:04:36 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
15:04:36 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
15:04:36 at java.lang.Thread.run(Thread.java:662)
15:04:36 Caused by: java.lang.NullPointerException
15:04:36 at hudson.maven.AbstractMavenBuilder$FilterImpl.executeAsync(AbstractMavenBuilder.java:174)
15:04:36 at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:128)
15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectSucceeded(Maven3Builder.java:378)
15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.projectSucceeded(Maven3Builder.java:352)
15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74)
15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91)
15:04:36 ... 10 more
Originally reported by banoss, imported from: NPE running Maven 3 job
- assignee:
kutzi
- status: Resolved
- priority: Critical
- component(s): core
- resolution: Fixed
- resolved: 2011-10-30T11:34:35+00:00
- votes: 1
- watchers: 4
- imported: 2025-11-24
Raw content of original issue
Getting this at the start of the build. Its reporting FAILURE building the parent module (aggregated poms) this is after upgrading from Jenkins 1.432 to 1.436. Reverting back to 1.432 problem goes away.
Config is a M3 project I've tried 1 or more threads with same result.
15:04:36 mavenExecutionResult exceptions not empty 15:04:36 message : Internal error: java.lang.NullPointerException 15:04:36 cause : null 15:04:36 Stack trace : 15:04:36 org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException 15:04:36 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) 15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) 15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167) 15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164) 15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 15:04:36 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 15:04:36 at java.lang.Thread.run(Thread.java:662) 15:04:36 Caused by: java.lang.NullPointerException 15:04:36 at hudson.maven.AbstractMavenBuilder$FilterImpl.executeAsync(AbstractMavenBuilder.java:174) 15:04:36 at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:128) 15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectSucceeded(Maven3Builder.java:378) 15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.projectSucceeded(Maven3Builder.java:352) 15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74) 15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) 15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91) 15:04:36 ... 10 more
- environment:
Slave on Windows 7 64-bit, Master on Solaris 10. Jenkins version 1.436.
Activity
jenkins-infra-bot commentedon Oct 24, 2011
Raw content of original comment:
Ouch
jenkins-infra-bot commentedon Oct 24, 2011
Raw content of original comment:
The build does happen on master or on a slave?
jenkins-infra-bot commentedon Oct 24, 2011
banoss:
Raw content of original comment:
Sorry, build is on slave. Deleted slave files and restarted when I upgraded Jenkins to ensure latest versions were copied. checked slave logs which look fine - no errors.
<===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.11
This is a Windows slave
Copied maven-agent.jar
Copied maven3-agent.jar
Copied maven3-interceptor.jar
Copied maven-interceptor.jar
Copied maven2.1-interceptor.jar
Copied plexus-classworld.jar
Copied classworlds.jar
Slave successfully connected and online
Also just tried running job on the (unix) master - same result.
Tried much simpler job similar config (ie parent pom and 3 modules) but that works fine...
jenkins-infra-bot commentedon Oct 25, 2011
Raw content of original comment:
So the obvious question is: can you track down the differences of the projects which trigger the failure?
jenkins-infra-bot commentedon Oct 25, 2011
banoss:
Raw content of original comment:
The one that fails is a much larger project (80 components - pom structure is 6 levels deep) the smaller test project is only 4 components - parent and 1 level of children.
The more interesting question is why can i up/downgrade between 1.436/1.432 and it builds fine on 1.432 but always fails on 1.436!
I will try versions of Jenkins in between and see where it starts to fail.
jenkins-infra-bot commentedon Oct 25, 2011
Raw content of original comment:
Try 1.434 and 1.435 first! I guess that it's was introduced in 1.435. Also, it should be enough to change the maven-plugin
jenkins-infra-bot commentedon Oct 26, 2011
banoss:
Raw content of original comment:
Ahh Kutzi, correct as always. 1.434 works fine; 1.435 is when this issue starts to occur.
jenkins-infra-bot commentedon Oct 26, 2011
Raw content of original comment:
Code changed in jenkins
User: Christoph Kutzinski
Path:
maven-plugin/src/main/java/hudson/maven/AbstractMavenBuilder.java
maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/jenkins/609b321e6ee0963908dddda048d572f2550e75aa
Log:
JENKINS-11458when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.jenkins-infra-bot commentedon Oct 26, 2011
Raw content of original comment:
Could you try http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/1244/artifact/maven-plugin/target/maven-plugin.hpi - once it has been build - if it fixes your issue?
jenkins-infra-bot commentedon Oct 26, 2011
Raw content of original comment:
Integrated in
jenkins_main_trunk #1244
JENKINS-11458when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.Christoph Kutzinski : 609b321e6ee0963908dddda048d572f2550e75aa
Files :
jenkins-infra-bot commentedon Oct 27, 2011
Raw content of original comment:
I'm having a trouble with 609b321e6ee0963908dddda048d572f2550e75aa.
Ubuntu Server 11.10 64bit
Oracle JDK 1.6.0_27
Maven 3.0.3
Reverting 609b321 make Jenkins build successfully.
jenkins-infra-bot commentedon Oct 27, 2011
Raw content of original comment:
Sorry.
Does this happen in Jenkins unit/integration test or when you're trying to build 'real' jobs?
jenkins-infra-bot commentedon Oct 27, 2011
Raw content of original comment:
There is no problem in building the master branch of Jenkins.
It is a real job to build Jenkins with maven3.
An NPE "channel must not be null!" also happens
when building other maven3 projects.
jenkins-infra-bot commentedon Oct 27, 2011
Raw content of original comment:
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
maven-plugin/src/main/java/hudson/maven/AbstractMavenBuilder.java
maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
maven-plugin/src/main/java/hudson/maven/MavenBuild.java
maven-plugin/src/main/java/hudson/maven/MavenBuildProxy.java
http://jenkins-ci.org/commit/jenkins/dc716da16bb400f741c1e650d0f3465bb70b4d18
Log:
JENKINS-11458Channel.current() is only available from the thread that's executing the remote call, and that's why we saw this original error, when Maven uses a thread pool to call into this method from another worker thread.jenkins-infra-bot commentedon Oct 27, 2011
Raw content of original comment:
Integrated in
jenkins_main_trunk #1248
JENKINS-11458Channel.current() is only available from the thread that's executing the remote call, and that's why we saw this original error, when Maven uses a thread pool to call into this method from another worker thread.Kohsuke Kawaguchi : dc716da16bb400f741c1e650d0f3465bb70b4d18
Files :
jenkins-infra-bot commentedon Oct 30, 2011
Raw content of original comment:
Code changed in jenkins
User: Christoph Kutzinski
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/f3d31af0516c4163c898dc0a9442e3f15f770d5b
Log:
changelog for
JENKINS-11458Compare: 9887593...f3d31af
jenkins-infra-bot commentedon Oct 30, 2011
Raw content of original comment:
Thanks to Kohsuke this should be fixed in 1.438
jenkins-infra-bot commentedon Oct 31, 2011
banoss:
Raw content of original comment:
Just checked 1.438-SNAPSHOT (private-10/30/2011 12:59 GMT-jenkins) and it is indeed fixed. Many thanks.
jenkins-infra-bot commentedon Oct 4, 2013
Raw content of original comment:
Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/maven/AbstractMavenBuilder.java
src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/maven-plugin/1c1415bc55874b5d753b904bfe5b9ac564ffbad7
Log:
JENKINS-11458when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.Originally-Committed-As: 609b321
jenkins-infra-bot commentedon Oct 4, 2013
Raw content of original comment:
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/main/java/hudson/maven/AbstractMavenBuilder.java
src/main/java/hudson/maven/Maven3Builder.java
src/main/java/hudson/maven/MavenBuild.java
src/main/java/hudson/maven/MavenBuildProxy.java
http://jenkins-ci.org/commit/maven-plugin/d541a16ed95f3f8f6dec0bdc41ebdbfad8067c54
Log:
JENKINS-11458Channel.current() is only available from the thread that's executing the remote call, and that's why we saw this original error, when Maven uses a thread pool to call into this method from another worker thread.Originally-Committed-As: dc716da