Build failure with Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher

[1eyed...@gmail.com]

Hello,

I have been searching for an answer to this problem, and what I've found so far refers to slaves and other terminology I don't know.  I am not an administrator, just someone who uses Jenkins to run builds for our Java projects.  We have one project that uses Maven, and we have just recently started getting errors that show:

[EnvInject] - Variables injected successfully.
Parsing POMs
Discovered a new module com.bc.woodCustomer:WoodCustomerBuild Wood Customer Build Project (Maven Build)
Discovered a new module com.bc.woodCustomer:WoodCustomerEar Wood Customer Ear
Discovered a new module com.bc.woodCustomer:WoodCustomerWeb Wood Customer Web
Modules changed, recalculating dependency graph
[WoodCustomerBuild] $ /opt/java//bin/java -cp /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/opt/maven/boot/plexus-classworlds-2.5.1.jar:/opt/maven/conf/logging jenkins.maven3.agent.Maven31Main /opt/maven /tmp/jetty-0.0.0.0-8090-jenkins.war--any-/webapp/WEB-INF/lib/remoting-2.32.jar /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 42886
Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher
	at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
	at jenkins.maven3.agent.Maven31Main.main(Maven31Main.java:138)
	at jenkins.maven3.agent.Maven31Main.main(Maven31Main.java:67)
ERROR: Failed to parse POMs
java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:189)
	at java.net.SocketInputStream.read(SocketInputStream.java:121)
	at java.io.FilterInputStream.read(FilterInputStream.java:133)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
	at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:133)
	at hudson.remoting.Channel.<init>(Channel.java:406)
	at hudson.remoting.Channel.<init>(Channel.java:402)
	at hudson.remoting.Channel.<init>(Channel.java:363)
	at hudson.remoting.Channel.<init>(Channel.java:359)
	at hudson.remoting.Channel.<init>(Channel.java:355)
	at hudson.slaves.Channels$1.<init>(Channels.java:71)
	at hudson.slaves.Channels.forProcess(Channels.java:71)
	at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:252)
	at hudson.maven.ProcessCache.get(ProcessCache.java:235)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:736)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:246)
Finished: FAILURE

This same configuration has worked previously.

We are using Jenkins version 1.535.

I read one post that said if you don't have anything in the workspace, the build succeeds. I have tried copying the configuration to a new job, and actually creating a new job, both of which have no workspace, and both of those get the same error.

Can anyone help me with this issue?

Thanks,

Chris

[1eyed...@gmail.com]

We ultimately got our server administrator to restart Jenkins, and now the builds are working.  If anybody out there has this same issue - try that first!

[Michael Giroux]

Disconnecting the slave, and then reconnecting solved the problem for us.  This causes jenkins to refresh the runtime jars on the slave.

[isov...@gmail.com]

thx,it works.

在 2016年8月30日星期二 UTC+8下午10:30:24，Michael Giroux写道：