It happens that builds fail with something like:
FATAL: Unable to call join. Invalid object ID 1583 java.lang.IllegalStateException: Unable to call join. Invalid object ID 1583 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:269) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:662)
This reduces chance to get successful matrix build. In this particular instance 4 out of 10 configurations in matrix build failed with this stacktrace upon requesting changes from scm.
- duplicates
-
JENKINS-23271 Intermittent Invalid Object ID in remoting module
-
- Resolved
-
[JENKINS-16393] "Unable to call join" build failures
Labels | New: remoting |
Component/s | New: remoting [ 15489 ] | |
Component/s | Original: core [ 15593 ] |
Workflow | Original: JNJira [ 147211 ] | New: JNJira + In-Review [ 176838 ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |