Hi,

I'm looking to fix this issue, or at least create a workaround for our
environment:

https://issues.jenkins-ci.org/browse/JENKINS-16824

Specifically, I'm thinking of deploying modified version of slave.jar,
where I wrap this Object.wait() call:

https://github.com/jenkinsci/remoting/blob/remoting-2.17/src/main/java/hudson/remoting/Request.java#L146

in try-catch and detect if InterruptedException is spurious. I hope someone
more familiar with innards of Jenkins and slave.jar could tell me, if there
is any way to detect, if InterruptedException should be just ignored and
wait resumed?

Would it be enough to just ignore any InterruptedException during the
wait() and rely on the conditions which already are in the while-loop
condition surrounding the wait()? It's ok for me even if this is bad in
some ways, as long as it does not actually break anything too badly and I
could use it as a short-term workaround, as the aborted builds are really
quite annoying...

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to