If ssh/jnlp connection dies remoting calls are stuck in an infinite loop.

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Seeing this happen with us frequently.  I realize that we've got an underlying issue to fix with the ssh/jnlp connection just dying for no reason... but we keep having these process stuck on Request.java:177 indefinitely till a bounce is done of jenkins.   Any way we could put a timeout or check to see if the channel is actually running?    

      "Workspace clean-up thread / waiting for system-tasks-xx.xx.xx.xx-aadeca16-3f43-47dc-b26d-41cad9d6891b id=12469479" daemon prio=5 TIMED_WAITING java.base@17.0.12/java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:1041) hudson.FilePath.act(FilePath.java:1229) hudson.FilePath.act(FilePath.java:1218) hudson.model.WorkspaceCleanupThread.execute(WorkspaceCleanupThread.java:102) hudson.model.AsyncPeriodicWork.lambda$doRun$0(AsyncPeriodicWork.java:102) hudson.model.AsyncPeriodicWork$$Lambda$998/0x000000008144b230.run(Unknown Source) java.base@17.0.12/java.lang.Thread.run(Thread.java:842)

            Assignee:
            Jeff Thompson
            Reporter:
            Michael Carter
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: