Details

Description

Hi folks,

Last week, I started to experience a weird issue with freezing/endless waiting of building jobs on slave machines. It first started with WinXP 32 bit slave, but I'm now experiencing the same problem also with WinXP 64 bit slave.

The symptoms are like this...
The job is started by SCM change or predefined time.
Both slave machines are correctly started (the last line, in their respective logs, says "Slave successfully connected and online").
Now the problem is, that the last line in console says "Building remotely on slave-name..." and there is just scrolling the progress circle. Nothing else happens. No GIT or SVN activity, no building, no testing, simply nothing and it stays like that until I kill the job manually.

Sometimes, the problem happens with just one machine, and the other one runs OK. But today it struck both machines.

Last week, when the problem started, I tried to update the Jenkins and both slaves with the most recent versions and latest plugins (except the "Git Client Plugin", because of a known issue with building history). Few hours all worked great, then the problem reappeared.

Please see the attached files with logs and thread dumps from both slave machines.

What struck me is the high number of threads started on both machines, which looks really weird? But I don't understand Jenkins that deep so I can't say for sure if it's normal or not?

Activity

Dave Taddei, can you confirm you are using the property hudson.remoting.RemoteClassLoader.force to force the load of com.sun.jna.Native. Also that you can see that the class is being loaded via the log of the slave.

BBVA
added a comment - 2016-08-22 09:55 Dave Taddei, can you confirm you are using the property hudson.remoting.RemoteClassLoader.force to force the load of com.sun.jna.Native. Also that you can see that the class is being loaded via the log of the slave.

Hi BBVA, it does not appear so but I am unsure where to look. Should this be set in the JAVA_ARGS for the master, slave or both? I was also under the impression that had been added to release 2.47 so didn't set anything.

Dave Taddei
added a comment - 2016-08-25 15:10 - edited Hi BBVA, it does not appear so but I am unsure where to look. Should this be set in the JAVA_ARGS for the master, slave or both? I was also under the impression that had been added to release 2.47 so didn't set anything.

Greg Smith
added a comment - 2016-10-28 04:14 We are using dynamic slaves, with the vcenter plugin. The vcenter plugin does not allow the specifications of any JVM options.
At least, I do not believe it does. Could the above change be made permanent, or set as the default for all slaves some how?

Jesse Glick
added a comment - 2017-12-18 13:43 Greg Smith et al.—see the last comment I left in JENKINS-39179 : I wrote a little plugin which might work around JNA deadlocks without needing individual configuration of static agents.