We also have been faced on the same problem.
We were obliged to restart several times slaves before they can be reused
(randomly).
For the record, which version of java on slave and master are you using ?

Our configuration :
Master : AIX 5.3 - java version "1.6.0" Java(TM) SE Runtime Environment
(build pap3260sr9-20101125_01(SR9)) (IBM)
Slaves : RHEL 5 - java "1.6.0_25" Java(TM) SE Runtime Environment (build
1.6.0_25-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed
mode)

I think the problem is caused by a different packaging of xercesImpl.jar in
master's JRE and slaves' JRE.

see
https://issues.jenkins-ci.org/browse/JENKINS-10238?focusedCommentId=165393#comment-165393

I've added the xercesImpl.jar implementation of the master directly in the
classpath of the slaves' launchers to be sure that the same packaging
of xercesImpl.jar is applyied in both cases.
I'm not sure to clearly understand the root cause, but since I applied this
solution the bug doesn't appear anymore (perhaps, I'm just a lucky guy for
2 months :-) ).

An opinion from a more experienced java developer on different types of JVM
would be interesting.

Michaël

2012/9/4 Anura S Nawarathna <anur...@gmail.com>

> I also has the same problem and disconnect and reconnect the slave solved
> the problem.
> Try this.
> Good Luck!
>
> On Friday, November 4, 2011 6:13:58 AM UTC+5:30, Jamie wrote:
>>
>> Hi all. I've not been able to find a solution to this one thus far so
>> am hoping I can crowd-source it somewhat. I have a Jenkins master
>> running on Linux and a slave running Mac OS X. The master/slave setup
>> is able to build XCode based projects but fails when I try and build
>> my Maven one. Slave launch method is 'Launch slave agents on Unix
>> machines via SSH'. Stack trace:
>>
>> arsing POMs
>> ERROR: Failed to parse POMs
>> hudson.util.IOException2: remote file operation failed: /Users/jenkins/
>> Documents/work/workspace/**recruiting at
>> hudson.remoting.Channel@**1552efb4:raut.apple.com
>>         at hudson.FilePath.act(FilePath.**java:781)
>>         at hudson.FilePath.act(FilePath.**java:767)
>>         at hudson.maven.**MavenModuleSetBuild
>> $RunnerImpl.parsePoms(**MavenModuleSetBuild.java:894)
>>         at hudson.maven.**MavenModuleSetBuild
>> $RunnerImpl.doRun(**MavenModuleSetBuild.java:644)
>>         at 
>> hudson.model.AbstractBuild$**AbstractRunner.run(**AbstractBuild.java:
>>
>> 460)
>>         at hudson.model.Run.run(Run.java:**1404)
>>         at 
>> hudson.maven.**MavenModuleSetBuild.run(**MavenModuleSetBuild.java:470)
>>
>>         at 
>> hudson.model.**ResourceController.execute(**ResourceController.java:
>>
>> 88)
>>         at hudson.model.Executor.run(**Executor.java:230)
>> Caused by: java.io.IOException: Remote call on raut.apple.com failed
>>         at hudson.remoting.Channel.call(**Channel.java:690)
>>         at hudson.FilePath.act(FilePath.**java:774)
>>         ... 8 more
>> Caused by: java.lang.**NoClassDefFoundError: Could not initialize class
>> hudson.maven.**MavenModuleSetBuild
>>         at hudson.maven.**MavenModuleSetBuild
>> $PomParser.invoke(**MavenModuleSetBuild.java:1156)
>>         at hudson.maven.**MavenModuleSetBuild
>> $PomParser.invoke(**MavenModuleSetBuild.java:1029)
>>         at hudson.FilePath$**FileCallableWrapper.call(**FilePath.java:2022)
>>
>>         at hudson.remoting.UserRequest.**perform(UserRequest.java:118)
>>         at hudson.remoting.UserRequest.**perform(UserRequest.java:48)
>>         at hudson.remoting.Request$2.run(**Request.java:287)
>>         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:680)
>> Finished: FAILURE
>>
>> The closest issue I found to this one was:
>>
>> http://stackoverflow.com/**questions/6653147/jenkins-**
>> slave-throws-classloading-**from-system-classloader-**disabled-exception<http://stackoverflow.com/questions/6653147/jenkins-slave-throws-classloading-from-system-classloader-disabled-exception>
>>
>> but that solution (delete the xercesImpl.jar in the Jenkins WEB-INF/
>> lib directory) didn't work for us.
>>
>> Any ideas? More information I can provide?
>
>

Reply via email to