Jenkins 1.399 fails with Asynchronous execution failure

[Terena Chinn-Fujii]

Hi,

In Jenkins 1.399, we were starting to run into the following error:

Waiting for Jenkins to finish collecting data
ERROR: Asynchronous execution failure
channel stopped
ERROR: Failed to parse POMs
java.io.IOException: Remote call on Channel to Maven [java, -Xmx1600m,
-cp, L:\hudson\plugins\maven-plugin\WEB-INF\lib\maven-
agent-1.399.jar;L:\java\apache-maven-2.2.1\boot\classworlds-1.1.jar,
hudson.maven.agent.Main, L:\java\apache-maven-2.2.1, L:
\glassfishv3\glassfish\domains\domain1\applications\hudson\WEB-INF\lib
\remoting-1.399.jar, L:\hudson\plugins\maven-plugin\WEB-INF\lib\maven-
interceptor-1.399.jar, 50543, L:\hudson\plugins\maven-plugin\WEB-INF
\lib\maven2.1-interceptor-1.2.jar] failed
at hudson.remoting.Channel.call(Channel.java:639)
at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.doRun(MavenModuleSetBuild.java:647)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
421)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:406)
at hudson.model.ResourceController.execute(ResourceController.java:
88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: java.lang.NoSuchMethodError:
org.apache.commons.codec.binary.Base64.<init>(I[B)V
at
org.apache.commons.codec.binary.Base64OutputStream.<init>(Base64OutputStream.java:
97)
at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:180)
at hudson.console.ConsoleNote.encodeTo(ConsoleNote.java:158)
at hudson.util.StreamTaskListener.annotate(StreamTaskListener.java:
157)
at hudson.util.StreamTaskListener._error(StreamTaskListener.java:132)
at hudson.util.StreamTaskListener.error(StreamTaskListener.java:141)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:183)
at hudson.maven.MavenModuleSetBuild
$Builder.call(MavenModuleSetBuild.java:872)
at hudson.maven.MavenModuleSetBuild
$Builder.call(MavenModuleSetBuild.java:803)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

I have since upgraded to Jenkins 1.400 but we're still seeing the same
error.

The Jenkins master (we're not running slaves at this time) is running
on Windows 2008 R2 Datacenter, GlassFish v3, JDK 1.6.0_21 32 bits, SVN
repository, and Maven 2.2.1 calling the following maven command:

clean javadoc:jar source:jar -Denablereporting=true deploy

It deploys the artifacts to an Archiva maven repository with no
problems and everything else seems to be fine with the build itself
until whatever else Jenkins does at the end of the build which is
reporting a "Finished: FAILURE".

Does anyone know what is causing this and how to resolve it?

Thanks,
Terena