[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Samuel Beaulieu commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Has anyone time to test with the new version of the swarm plugin (2.1)? https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
Mikael Gaunin edited a comment on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
Fyi, the workaround asking the java downgrade to version 7 works well. As a summary:* Master and slaves running with Java 8 => some builds fails with such exception:{quote}10:14:43 ERROR: Build step failed with exception10:14:43 java.lang.IllegalStateException (http://stacktrace.jenkins-ci.org/search?query=java.lang.IllegalStateException) : Invalid object ID 52 iota=53{quote}* +Upgrading+ them to the +latest Java 8 release+ (here 1.8.0_92) *does not fix the issue*.* +Downgrading+ Master and slaves to +Java 7+ (here 1.7.0_79) *solved the problem*.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Mikael Gaunin commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Fyi, the workaround asking the java downgrade to version 7 works well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Ondrej Kunc commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I ran in same issue: jenkins 1.652 linux derived from ubuntu trusty java version "1.8.0_51" Java(TM) SE Runtime Environment (build 1.8.0_51-b16) Java HotSpot(TM) Server VM (build 25.51-b03, mixed mode) I also see it only like 1 of 1000 builds for matrix projects. ERROR: Build step failed with exception java.lang.IllegalStateException: Invalid object ID 31032 iota=31033 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:633) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:120) 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:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to PEARF_172.24.200.196(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:220) at hudson.remoting.Channel.call(Channel.java:781) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) at com.sun.proxy.$Proxy49.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:991) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:135) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.Exception: Object was recently deallocated #31032 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Mon Apr 25 18:57:07 UTC 2016 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:629) at hudson.remoting.Channel.export(Channel.java:620) at hudson.remoting.Channel.export(Channel.java:590) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1150) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) 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:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module As previously, I have no spare personal time to work on this issue. Sorry about that, but I assure you there are serious reasons for that. When I agreed to take the ownership of this library, I explicitly notified the previous maintainer that I won't be able to dedicate my personal time. My work plans are being determined by the management. The issue requires several days without distraction, so it's hard to get it scheduled. Actually, I have already made an attempt to fix it, but I was not very successful. The "good" news is that it's high in the backlogs, so it may be taken in the short-term. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Christoph Kulla commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg, is there a plan when this issue will be fixed? I have the feeling that many users are hit by this problem. Please give us a short update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Joachim Nilsson commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module This happened to us as well today. 1.647 RHEL 6.5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Joachim Nilsson edited a comment on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module This happened to us as well today. 1.647RHEL 6.5 Java8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Michael Schulz commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Any updates whats the solving state for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title John Lengeling commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We were running into this issue after we upgraded to Java 1.8.60 in January with Jenkins 1.632. We downgraded to Java on the master to 1.7.80 and the "iota" errors went away. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Kevin Yu commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Just an update: After we downgrade from java8 to java7, we no longer see the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Kevin Yu edited a comment on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Just an update:After we downgrade downgraded from java8 to java7, we no longer see the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
Kevin Yu edited a comment on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
We started to see this issue the first time.We have a matrix job with 130 variants and the problem happened in post build when it's evaluating whether the current build status is success before triggering other things.{code:java} eb 09, 2016 7:12:00 AM org.jenkins_ci.plugins.run_condition.BuildStepRunner logEvaluateExceptionWARNING: Exception caught evaluating condition: [java.lang.IllegalStateException: Invalid object ID 901 883 iota= 902 884 ], action = [Fail the build] Build step 'Execute a set of scripts' changed build result java.lang.IllegalStateException: Invalid object ID 883 iota=884at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386)at hudson.remoting.ExportTable.get(ExportTable.java:330)at hudson.remoting.Channel.getExportedObject(Channel.java:633)at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)at hudson.remoting.UserRequest.perform(UserRequest.java:120)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:68)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)at ..remote call to FAILURE jenkins-slave4(192.168.100.153)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)at hudson.remoting.Channel.call(Channel.java:781)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)at com.sun.proxy.$Proxy50.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:991)at hudson.Launcher$ProcStarter.join(Launcher.java:388)at org.jenkins_ci.plugins.run_condition.contributed.CommandInterperterCondition.runPerform(CommandInterperterCondition.java:89)at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.evaluate(BuildStepRunner.java:107)at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:147)at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:133)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)at org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:82)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)at hudson.model.Build$BuildExecution.post2(Build.java:185)at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)at hudson.model.Run.execute(Run.java:1763)at hudson.matrix.MatrixRun.run(MatrixRun.java:146)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.Exception: Object was recently deallocated
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Kevin Yu commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We started to see this issue the first time. We have a matrix job with 130 variants and the problem happened in post build when it's evaluating whether the current build status is success before triggering other things. Exception caught evaluating condition: [java.lang.IllegalStateException: Invalid object ID 901 iota=902], action = "" the build] Build step 'Execute a set of scripts' changed build result to FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Kyle Leinen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We are also seeing this issue, but we didn't change Jenkins versions, just after updated to Oracle Java 1.8. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Hi Christoph, My apologies for the delay, but I still have no time to work on it. I'll update the status when I find a timeslot. Currently it's not "in progress". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Jon Whitcraft commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg Nenashev, Can you possibly share your steps for the reproducible scenario, so maybe someone else can fix it? Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Jon Whitcraft My reproduction steps are based on the closed-source plugins from CloudBees Jenkins Platform. But the case from Z. S. also has a good reproduction rate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Christoph Kulla commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg, any update on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
Jon Whitcraft edited a comment on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
We just starting run into this with using the CloudBees Docker Custom Build Environment Plugin to run our jobs inside of a docker container.{ quote code }10:50:53 ERROR: Build step failed with exception10:50:53 java.lang.IllegalStateException: Invalid object ID 125 iota=12610:50:53 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386)10:50:53 at hudson.remoting.ExportTable.get(ExportTable.java:330)10:50:53 at hudson.remoting.Channel.getExportedObject(Channel.java:633)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:120)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:48)10:50:53 at hudson.remoting.Request$2.run(Request.java:326)10:50:53 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)10:50:53 at java.util.concurrent.FutureTask.run(FutureTask.java:262)10:50:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)10:50:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)10:50:53 at java.lang.Thread.run(Thread.java:745)10:50:53 at ..remote call to docker 1.9.1 ami (i-07e75b8e)(Native Method)10:50:53 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)10:50:53 at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)10:50:53 at hudson.remoting.Channel.call(Channel.java:781)10:50:53 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)10:50:53 at com.sun.proxy.$Proxy104.join(Unknown Source)10:50:53 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:992)10:50:53 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)10:50:53 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)10:50:53 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)10:50:53 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)10:50:53 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)10:50:53 at hudson.model.Build$BuildExecution.build(Build.java:205)10:50:53 at hudson.model.Build$BuildExecution.doRun(Build.java:162)10:50:53 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)10:50:53 at hudson.model.Run.execute(Run.java:1741)10:50:53 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)10:50:53 at hudson.model.ResourceController.execute(ResourceController.java:98)10:50:53 at hudson.model.Executor.run(Executor.java:408)10:50:53 Caused by: java.lang.Exception: Object was recently deallocated10:50:53 #125 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess]10:50:53 Created at Mon Jan 18 18:50:52 UTC 201610:50:53 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99)10:50:53 at hudson.remoting.ExportTable.export(ExportTable.java:305)10:50:53 at hudson.remoting.Channel.internalExport(Channel.java:629)10:50:53 at hudson.remoting.Channel.export(Channel.java:620)10:50:53 at hudson.remoting.Channel.export(Channel.java:590)10:50:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1151)10:50:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1114)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:120)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:48)10:50:53 at hudson.remoting.Request$2.run(Request.java:326)10:50:53 at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Jon Whitcraft commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We just starting run into this with using the CloudBees Docker Custom Build Environment Plugin to run our jobs inside of a docker container. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
Jon Whitcraft edited a comment on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
We just starting run into this with using the CloudBees Docker Custom Build Environment Plugin to run our jobs inside of a docker container. {quote}10:50:53 ERROR: Build step failed with exception10:50:53 java.lang.IllegalStateException: Invalid object ID 125 iota=12610:50:53 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386)10:50:53 at hudson.remoting.ExportTable.get(ExportTable.java:330)10:50:53 at hudson.remoting.Channel.getExportedObject(Channel.java:633)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)10:50:53 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:120)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:48)10:50:53 at hudson.remoting.Request$2.run(Request.java:326)10:50:53 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)10:50:53 at java.util.concurrent.FutureTask.run(FutureTask.java:262)10:50:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)10:50:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)10:50:53 at java.lang.Thread.run(Thread.java:745)10:50:53 at ..remote call to docker 1.9.1 ami (i-07e75b8e)(Native Method)10:50:53 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)10:50:53 at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)10:50:53 at hudson.remoting.Channel.call(Channel.java:781)10:50:53 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)10:50:53 at com.sun.proxy.$Proxy104.join(Unknown Source)10:50:53 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:992)10:50:53 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)10:50:53 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)10:50:53 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)10:50:53 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)10:50:53 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)10:50:53 at hudson.model.Build$BuildExecution.build(Build.java:205)10:50:53 at hudson.model.Build$BuildExecution.doRun(Build.java:162)10:50:53 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)10:50:53 at hudson.model.Run.execute(Run.java:1741)10:50:53 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)10:50:53 at hudson.model.ResourceController.execute(ResourceController.java:98)10:50:53 at hudson.model.Executor.run(Executor.java:408)10:50:53 Caused by: java.lang.Exception: Object was recently deallocated10:50:53 #125 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess]10:50:53 Created at Mon Jan 18 18:50:52 UTC 201610:50:53 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99)10:50:53 at hudson.remoting.ExportTable.export(ExportTable.java:305)10:50:53 at hudson.remoting.Channel.internalExport(Channel.java:629)10:50:53 at hudson.remoting.Channel.export(Channel.java:620)10:50:53 at hudson.remoting.Channel.export(Channel.java:590)10:50:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1151)10:50:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1114)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:120)10:50:53 at hudson.remoting.UserRequest.perform(UserRequest.java:48)10:50:53 at hudson.remoting.Request$2.run(Request.java:326)10:50:53 at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Current state: I have a reproducible scenario for this issue I've spent some time on it's debugging, but unfortunately I had not enough spare time to finish it and to draft a fix The issue is in my short-list, so I'm going to handle it once I finish the Ownership plugin release or when my company assigns me to work on it during the working time Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Christoph Kulla commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I'm blocked by this issues as well. Seeing this in matrix jobs and copying artifacts. Please let us know how you proceed with this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Christoph Kulla edited a comment on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I'm blocked by this issues issue as well. Seeing this in matrix jobs and copying artifacts. Please let us know how you proceed with this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
R. Tyler Croy commented on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
For my use-case I'm going to go ahead and remove my use of parallel { }}} in my {{Jenkinsfile so I can be unblocked, but I'm looking forward to this one-day being fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Eduard Weiss commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Have same problem Jenkins 1.6.3.5 Master and Slave running in docker container java.lang.IllegalStateException: Invalid object ID 17979 iota=17980 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:630) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to deimsv0302(rel)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:992) at hudson.Launcher$ProcStarter.join(Launcher.java:389) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:77) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:108) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:143) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:358) at hudson.model.Run.getEnvironment(Run.java:2232) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:941) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:481) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.Exception: Object was recently deallocated #17979 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Dec 15 22:43:06 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:626) at hudson.remoting.Channel.export(Channel.java:617) at hudson.remoting.Channel.export(Channel.java:587) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1151) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Dao Lam commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg Nenashev Any updates on this? Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Thomas De Schampheleire Yes I'm looking at the issue, but currently there is no ETA. We firstly want to get a scenario with a high reproduction rate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Thomas De Schampheleire commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg Nenashev Understood, thanks. I'm looking forward to more details when you have them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Thomas De Schampheleire commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Oleg Nenashev: thanks for the feedback. With this reproduction scenario, given that you are the assignee, does this mean you are currently looking at this? Have you been able to zoom in on the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Yep, looks to be similar to what we've seen with R Tyler Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Z. S. commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module So we've been plagued by this issue a long time. And have some good tips how to reproduce it .. Get a matrix job with 10+ jobs .. and make each one copy an artifact like a big jar (hundreds of megs) from another job in jenkins. The issue seems to happen when all the matrix jobs at the same time pull the artifact. We reduce the problem by putting some sleeps in the matrix jobs to make sure it doesnt run at the same time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Thomas De Schampheleire updated an issue Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Thomas De Schampheleire Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Thomas De Schampheleire commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Raising the priority to Blocker: for a continuous-integration application as Jenkins, one expects test runs to be reliable. We are hitting this problem very regularly recently, such that the job status is no longer reliable (too many false positives). The issue has been open for a long time without apparent progress. Kohsuke Kawaguchi Oleg Nenashev What is the current status of this bug? I haven't seen 'official' feedback on this issue. What can be done to get this issue resolved? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Thomas De Schampheleire edited a comment on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Raising the priority to Blocker: for a continuous-integration application as Jenkins, one expects test runs to be reliable. We are hitting this problem very regularly recently, such that the job status is no longer reliable (too many false positives). The issue has been open for a long time without apparent progress.[~kohsuke] , [~oleg_nenashev] : What is the current status of this bug? I haven't seen 'official' feedback on this issue.What can be done to get this issue resolved? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title R. Tyler Croy commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I've got a reproduction case using Workflow with parallel nodes "unstash"ing some contents from the same "stash" in Workflow: Using this Jenkinsfile running on a Jenkins master with the Docker plugin. The docker slave image is evarga/jenkins-slave with the following additional system packages installed: git, zlibc, ruby. jenkins.log from the master: Dec 09, 2015 2:52:58 PM org.jenkinsci.plugins.workflow.cps.CpsStepContext onFailure WARNING: already completed CpsStepContext[21]:Owner[jenkins-infra/staging/25:jenkins-infra/staging #25] java.lang.IllegalStateException: java.lang.InterruptedException at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:314) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.onFailure(CpsBodySubContext.java:63) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onFailure(BodyExecutionCallback.java:124) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:294) at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:106) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:274) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:74) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:183) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:181) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:979) at hudson.FilePath.act(FilePath.java:968) at hudson.FilePath.untarFrom(FilePath.java:718) at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:111) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module R. Tyler Croy managed to reproduce the issue using this WF script: https://github.com/jenkins-infra/jenkins-infra/blob/staging/Jenkinsfile . He used Docker cloud with nodes with a single executor. The issue happens frequently when you uncomment unstash in both clauses. Single unstash leads to another issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Michael Schulz commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Got a likely problem too. Comes the first time these day. Using 1.619 ERROR: Build step failed with exception java.lang.IllegalStateException: Unable to call join. Invalid object ID 308 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:294) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:281) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:240) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to e71c7-004360_Saga(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy62.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:992) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Hans-Juergen Hafner commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I got this exception after update of Jenkins from 1.620 to 1.634 and Java on master from jdk1.7.0_45 to jdk1.8.0_66. Slaves still use Java SE RE 1.7.0_03-b04. ClearCase plug-in is not installed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Radosław Palczyński updated an issue Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Radosław Palczyński Environment: 1.544.2, 1.563 , 1.625.1 - Windows or Linux Master, various slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Ben Hines updated an issue Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Ben Hines Environment: 1.544.2, 1.563 - Windows XP or Linux Master, various slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Radosław Palczyński commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I just got it on 1.625.1 00:29:47 ERROR: Build step failed with exception 00:29:47 java.lang.IllegalStateException: Invalid object ID 1813 iota=1814 00:29:47 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) 00:29:47 at hudson.remoting.ExportTable.get(ExportTable.java:330) 00:29:47 at hudson.remoting.Channel.getExportedObject(Channel.java:630) 00:29:47 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599) 00:29:47 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) 00:29:47 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) 00:29:47 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:29:47 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:29:47 at hudson.remoting.Request$2.run(Request.java:326) 00:29:47 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:29:47 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 00:29:47 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 00:29:47 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 00:29:47 at java.lang.Thread.run(Thread.java:745) 00:29:47 at ..remote call to nobel_nmel_ft_170_01(Native Method) 00:29:47 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) 00:29:47 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 00:29:47 at hudson.remoting.Channel.call(Channel.java:778) 00:29:47 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) 00:29:47 at com.sun.proxy.$Proxy48.join(Unknown Source) 00:29:47 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:992) 00:29:47 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) 00:29:47 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) 00:29:47 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) 00:29:47 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:29:47 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 00:29:47 at hudson.model.Build$BuildExecution.build(Build.java:205) 00:29:47 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 00:29:47 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) 00:29:47 at hudson.model.Run.execute(Run.java:1741) 00:29:47 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 00:29:47 at hudson.model.ResourceController.execute(ResourceController.java:98) 00:29:47 at hudson.model.Executor.run(Executor.java:408) 00:29:47 Caused by: java.lang.Exception: Object was recently deallocated 00:29:47 #1813 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] 00:29:47 Created at Fri Nov 06 23:29:46 UTC 2015 00:29:47 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) 00:29:47 at hudson.remoting.ExportTable.export(ExportTable.java:305) 00:29:47 at hudson.remoting.Channel.internalExport(Channel.java:626) 00:29:47 at hudson.remoting.Channel.export(Channel.java:617) 00:29:47 at hudson.remoting.Channel.export(Channel.java:587) 00:29:47 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1151) 00:29:47 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1114) 00:29:47 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:29:47 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:29:47 at hudson.remoting.Request$2.run(Request.java:326) 00:29:47 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:29:47 at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Franck Derunes commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module having this issue using Jenkins ver. 1.617 everyday using linux MINT slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Rasmus Pedersen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I've also seen it on a freestyle job now running 1.609.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Ben Furtado commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Getting the same error on 1.632. Any ETA for resolution? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Zilvinas Saltys commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Same problem on Jenkins ver. 1.609.3 java.lang.IllegalStateException: Invalid object ID 65341 iota=65342 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:630) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to Mega Slave2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) at com.sun.proxy.$Proxy70.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Caused by: java.lang.Exception: Object was recently deallocated #65341 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Fri Sep 25 13:09:11 UTC 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:626) at hudson.remoting.Channel.export(Channel.java:617) at hudson.remoting.Channel.export(Channel.java:587) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Released at Fri Sep 25 13:09:11 UTC 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:414) at hudson.remoting.Channel.unexport(Channel.java:638) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Rasmus Pedersen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I'm experiencing this on 1.609.3 on a Windows Server 2008 R2 running a Jenkins slave as a service. I've only seen it on matrix builds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title A C commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Seeing this on Jenkins 1.626 as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Henri Gomez commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Same problem here : Jenkins 1.580.3 (hosted on linux) Windows 2012 R2 (as slave) 05:00:02 java.lang.IllegalStateException: Invalid object ID 136 iota=137 05:00:02 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) 05:00:02 at hudson.remoting.ExportTable.get(ExportTable.java:324) 05:00:02 at hudson.remoting.Channel.getExportedObject(Channel.java:604) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) 05:00:02 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 05:00:02 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 05:00:02 at hudson.remoting.Request$2.run(Request.java:324) 05:00:02 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 05:00:02 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 05:00:02 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 05:00:02 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 05:00:02 at java.lang.Thread.run(Thread.java:745) 05:00:02 at ..remote call to winslave04(Native Method) 05:00:02 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) 05:00:02 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 05:00:02 at hudson.remoting.Channel.call(Channel.java:752) 05:00:02 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) 05:00:02 at com.sun.proxy.$Proxy71.join(Unknown Source) 05:00:02 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) 05:00:02 at hudson.Launcher$ProcStarter.join(Launcher.java:388) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title J John commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Saw this in windows master/slave. Jenkins ver: 1.608 java.lang.IllegalStateException: Invalid object ID 72 iota=73 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.get(ExportTable.java:324) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to apim-jenkins-s3(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy49.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.lang.Exception: Object was recently deallocated #72 (ref.0) : [hudson.Launcher$RemoteProcess] Created at Wed Jul 29 12:28:51 PDT 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:93) at hudson.remoting.ExportTable.export(ExportTable.java:299) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Released at Wed Jul 29 12:28:51 PDT 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:376) at hudson.remoting.Channel.unexport(Channel.java:612) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Andy Johns commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I may also be seeing this issue, or a similar issue: Environment: Jenkins ver. 1.596.1 Master: Mac OSX 10.9.5 Slaves: Mac OSX 10.9.5 and 10.10.3 as VMWare VMs Log snippet: FATAL: Invalid object ID 1675 iota=1676 java.lang.IllegalStateException: Invalid object ID 1675 iota=1676 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to YosemiteXCode6.3(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy78.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:359) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1675 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Wed Jun 24 16:17:50 PDT 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Released at Wed Jun 24 16:17:50 PDT 2015 at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Systems Administration commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Intermittently here as well: Jenkins 1.580.3 Ubuntu 14.04.2 64 bit Zulu 8.7.0.5-linux64 (build 1.8.0_45-b14) identical slave Please let us know should you need any additional logs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module This happens intermittently for me. Jenkins 1.596.2 Windows 2012 R2 (64-bit) master Windows 7 (32bit) slave Java: Oracle 1.8 java.lang.IllegalStateException: Invalid object ID 182 iota=183 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to vme-sv-exe-d12(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy73.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at org.jenkinsci.plugins.managedscripts.ScriptBuildStep.perform(ScriptBuildStep.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #182 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Released at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@17b6a6d created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Dell Green commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module Same happening to me. Happens on various slaves from mac to linux with varying specs. Jenkins 1.598 Latest fail: Mac OS X: 10.7.5 slave Java: Oracle 1.7.0_71 ERROR: Build step failed with exception java.lang.IllegalStateException: Invalid object ID 1224 iota=1225 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to Jenkins Slave 003 Mac(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy76.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at hudson.plugins.gradle.Gradle.performTask(Gradle.java:262) at hudson.plugins.gradle.Gradle.perform(Gradle.java:116) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1224 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Mon Apr 13 09:14:50 BST 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Released at Mon Apr 13 09:14:50 BST 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@4241183 created at at hudson.remoting.Command.init(Command.java:67) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Paul Brinkmann commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module I've seen this error a couple of times on our systems - Jenkins 1.580.3 with Linux master/SSH slaves, Oracle JDK 1.8.0_2 FATAL: Invalid object ID 6964 iota=6965 java.lang.IllegalStateException: Invalid object ID 6964 iota=6965 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.get(ExportTable.java:324) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to Docker02(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) at com.sun.proxy.$Proxy49.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #6964 (ref.0) : [hudson.Launcher$RemoteProcess] Created at Fri Mar 27 13:38:30 PDT 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:93) at hudson.remoting.ExportTable.export(ExportTable.java:299) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Released at Fri Mar 27 13:38:30 PDT 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:376) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@283bd1ca created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.UnexportCommand.init(UnexportCommand.java:33)
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
pascal_martin commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module Same issiue with Jenkins ver. 1.580.3 on windows FATAL: Invalid object ID 5581 iota=5582 java.lang.IllegalStateException: Invalid object ID 5581 iota=5582 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.get(ExportTable.java:324) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to DEV-BLD03(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) at com.sun.proxy.$Proxy68.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #5581 (ref.0) : hudson.Launcher$RemoteProcess Created at Thu Mar 12 14:05:10 EDT 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:93) at hudson.remoting.ExportTable.export(ExportTable.java:299) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Thu Mar 12 14:05:10 EDT 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:376) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@656783a5 created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module is there any update for this issue? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Richard Geary commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module This is occured for us today, on a Fedora 20 master, RHEL5 slave 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl updated JENKINS-23271 Intermittent Invalid Object ID in remoting module Upping this to critical because it's killing lots of my builds. Change By: Alex Earl (10/Feb/15 4:47 PM) Priority: Major Critical 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija edited a comment on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598. Any suggestion? thnx! java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=hudson.Launcher$RemoteProcess Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598. Any suggestion? thnx! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija edited a comment on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598 and Java8u31. Any suggestion? thnx! java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=hudson.Launcher$RemoteProcess Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by:
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module I'm getting this as well, but the sleep doesn't seem to be helping at all. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Mark Gollin commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module I have semi-confirmed that it is output from a shell script execution in a SSH controlled slave, specifically output extremely soon after the shell process launch that triggers this case. I inserted: sleep 1 ..at the top of every shell block in my projects and have no run approximately 200-300 builds without error (before this was repro'ing about 1 in 40). If you are encountering this problem, this workaround may be helpful. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Mark Gollin commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module Also seeing this issue on OS X Yosemite slave which is connected through SSH. The Perl script was likely trying to send output at the time. AXPAppBuild $ /bin/sh -xe /var/folders/ft/t3f3yt350bxg5_9dbvm_0p10gz/T/hudson8162295933868013475.sh + cd common/Platform/BuildTools + /usr/bin/perl PostJenkinsBuild.pl TestFlightRequestFlavor FATAL: Invalid object ID 89568 iota=89569 java.lang.IllegalStateException: Invalid object ID 89568 iota=89569 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to axpBuildNode(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy84.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #89568 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=hudson.Launcher$RemoteProcess Created at Tue Dec 02 15:31:33 PST 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Released at Tue Dec 02 15:31:33 PST 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Christian Symmons commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module Hi, we are seeing the same issue on a single OSX Client (Linux Master Server). Version 1.572. I've noticed it on two builds this morning. At the time, the build script was doing an untar in the command shell. x lib/QtXmlPatterns.framework/Versions/Current/Headers/qxmlnamepool.hFATAL: Invalid object ID 473 iota=474 java.lang.IllegalStateException: Invalid object ID 473 iota=474 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:304) at hudson.remoting.ExportTable.get(ExportTable.java:288) at hudson.remoting.Channel.getExportedObject(Channel.java:596) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) 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:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.Exception: Object was recently deallocated #473 (ref.0) : hudson.Launcher$RemoteLaunchCallable$1 Created at Thu Nov 06 02:55:27 GMT 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:91) at hudson.remoting.ExportTable.export(ExportTable.java:266) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.Channel.export(Channel.java:583) at hudson.remoting.Channel.export(Channel.java:553) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1078) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) 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:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Released at Thu Nov 06 02:55:28 GMT 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:332) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@52a2a0cb created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.UnexportCommand.init(UnexportCommand.java:33) at hudson.remoting.RemoteInvocationHandler.finalize(RemoteInvocationHandler.java:229) at java.lang.System$2.invokeFinalize(System.java:1267) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:98) at java.lang.ref.Finalizer.access$100(Finalizer.java:34) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:210) at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:297) ... 14 more Caused by: Released at Thu Nov 06 02:55:28 UTC 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:332) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by:
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Daniel Beck updated JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Daniel Beck (17/Oct/14 12:31 PM) Summary: Intermittent Ivalid Invalid ObjectIDinremotingmodule 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
