Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73619

Build job randomly fails while connecting to an agent with error Invalid object ID

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core, remoting

      During a Jenkins build job execution, an error occurs associated with the Git checkout step which has caused multiple build job failures. The error happens intermittently and appears to be related to an invalid object ID caused by a recently deallocated object. Below is the stack trace of the error for more detailed insight:

       

      java.lang.Exception: Object was recently deallocated
          #35 (ref.0) : object=null type=hudson.plugins.git.GitAPI interfaces=[hudson.plugins.git.IGitAPI]
      	at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:431)
      Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-10-47-2-89.us-west-2.compute.internal/10.47.2.89:44254
      		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1784)
      		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
      		at hudson.remoting.Channel.call(Channel.java:1000)
      		at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
      		at com.sun.proxy.$Proxy131.withRepository(Unknown Source)
      		at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:261)
      		at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordCommitsSincePreviousBuild(GitCheckoutListener.java:125)
      		at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordNewCommits(GitCheckoutListener.java:100)
      		at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordNewCommits(GitCheckoutListener.java:71)
      		at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.onCheckout(GitCheckoutListener.java:49)
      		at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:654)
      		at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85)
      		at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521)
      		at hudson.model.Run.execute(Run.java:1900)
      		at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
      		at hudson.model.ResourceController.execute(ResourceController.java:101)
      		at hudson.model.Executor.run(Executor.java:442)
      Caused: java.util.concurrent.ExecutionException: Invalid object ID 35 iota=38
      	at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:443)
      	at hudson.remoting.ExportTable.get(ExportTable.java:360)
      	at hudson.remoting.Channel.getExportedObject(Channel.java:824)
      	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:915)
      	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:902)
      	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:853)
      	at hudson.remoting.UserRequest.perform(UserRequest.java:211)
      	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
      	at hudson.remoting.Request$2.run(Request.java:376)
      	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
      	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
      	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
      	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:126)
      	at java.base/java.lang.Thread.run(Thread.java:829)
      Caused: hudson.remoting.RemotingSystemException
      	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:301)
      	at com.sun.proxy.$Proxy131.withRepository(Unknown Source)
      	at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:261)
      	at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordCommitsSincePreviousBuild(GitCheckoutListener.java:125)
      	at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordNewCommits(GitCheckoutListener.java:100)
      	at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.recordNewCommits(GitCheckoutListener.java:71)
      	at io.jenkins.plugins.forensics.git.reference.GitCheckoutListener.onCheckout(GitCheckoutListener.java:49)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:654)
      Caused: java.io.IOException
      	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:656)
      	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521)
      	at hudson.model.Run.execute(Run.java:1900)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
      	at hudson.model.ResourceController.execute(ResourceController.java:101)
      	at hudson.model.Executor.run(Executor.java:442) 

       

      Steps to Reproduce:

      1. Initiate a Jenkins pipeline which involves a Git checkout step.
      2. Observe the failure during the default checkout phase.
      3. Trace the error logs to identify the "Invalid object ID" message.

          [JENKINS-73619] Build job randomly fails while connecting to an agent with error Invalid object ID

          Mark Waite added a comment -

          Does the same failure happen with a current release of Jenkins and with current Jenkins plugins?

          Mark Waite added a comment - Does the same failure happen with a current release of Jenkins and with current Jenkins plugins?

          Apoorva added a comment -

          Hi markewaite, I don't have that data right now. We have plans to upgrade our production Jenkins instance to the latest version in a month or so. Until then, we won't be able to test this job.

          I will update you once we do the upgrade and if we are able to resolve this issue or not.

          Apoorva added a comment - Hi markewaite , I don't have that data right now. We have plans to upgrade our production Jenkins instance to the latest version in a month or so. Until then, we won't be able to test this job. I will update you once we do the upgrade and if we are able to resolve this issue or not.

            jthompson Jeff Thompson
            apoorva_m Apoorva
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: