[JIRA] (JENKINS-16393) "Unable to call join" build failures

Thu, 17 Jan 2013 06:43:05 -0800

Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 17/Jan/13 2:42 PM
Description:

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.
Environment: Jenkins 1.498 on RHEL 5 x86_64
Project: Jenkins
Priority: Major Major
Reporter: Krzysztof Malinowski
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to