java.lang.InterruptedException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Jenkins is running on a windows 2003 server In the job config postbuild task part: log text : . script : dir When the job is successed or failed, the postbuild task works fine When the job is aborted (manually stopped or timeout case) I get this kind of logs: Running script :dir [workspace] $ cmd /c call C:\Users\XXX\AppData\Local\Temp\2\hudson13287273761205392.bat Exception when executing the batch command : null Build step 'Post build task' marked build as failure Finished: ABORTED C:\Users\XXX\AppData\Local\Temp\2 is the java.io.tmpdir data I ran a non-stop script listing files in this folder, the temp script hudsonxxxxxxxx.bat is never written in this folder in the jenkins log I have a java exception generated each time a job is aborted : java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Native Method) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) It is a main issue in my professional project. From my web research it appears that post build task is supposed to work fine even when the job is aborted
    via by william vilpoix,
  • Jenkins is running on a windows 2003 server In the job config postbuild task part: log text : . script : dir When the job is successed or failed, the postbuild task works fine When the job is aborted (manually stopped or timeout case) I get this kind of logs: Running script :dir [workspace] $ cmd /c call C:\Users\XXX\AppData\Local\Temp\2\hudson13287273761205392.bat Exception when executing the batch command : null Build step 'Post build task' marked build as failure Finished: ABORTED C:\Users\XXX\AppData\Local\Temp\2 is the java.io.tmpdir data I ran a non-stop script listing files in this folder, the temp script hudsonxxxxxxxx.bat is never written in this folder in the jenkins log I have a java exception generated each time a job is aborted : java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Native Method) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) It is a main issue in my professional project. From my web research it appears that post build task is supposed to work fine even when the job is aborted
    via by william vilpoix,
  • After the build times out the final message is "Finished: ABORTED". If there was still a lot of data on the Standard Out stream, then the time out message gets lost in the gobs of text so that it reads: <TEXT> Build timed out (after 3 minutes). Marked the build as aborted. <TONS OF TEXT> Build was aborted Finished: ABORTED In this event, it is not obvious to the users why the build was aborted since the "timed out" message is lost in the remaining standard out text. To add the confusion, if the user views the Jenkins error log to try to determine the cause for the abort, there is an "InterruptedException" that is raised that makes it appear as though Jenkins aborted the build due to an unexpected occurrence. Modifying the Finished message to say something like "Finished: TIMED OUT" would make it very clear to any user why the build stopped regardless of where the other time out message is displayed. Also the exception in the Jenkins error log should be caught if it is an expected error, so that users are not left thinking Jenkins failed unexpectedly. Errr log: INFO: TEST #1 aborted java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Native Method) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Launcher$ProcStarter.join(Launcher.java:336) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459) at hudson.model.Run.run(Run.java:1376) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)
    via by pixman20,
  • After the build times out the final message is "Finished: ABORTED". If there was still a lot of data on the Standard Out stream, then the time out message gets lost in the gobs of text so that it reads: <TEXT> Build timed out (after 3 minutes). Marked the build as aborted. <TONS OF TEXT> Build was aborted Finished: ABORTED In this event, it is not obvious to the users why the build was aborted since the "timed out" message is lost in the remaining standard out text. To add the confusion, if the user views the Jenkins error log to try to determine the cause for the abort, there is an "InterruptedException" that is raised that makes it appear as though Jenkins aborted the build due to an unexpected occurrence. Modifying the Finished message to say something like "Finished: TIMED OUT" would make it very clear to any user why the build stopped regardless of where the other time out message is displayed. Also the exception in the Jenkins error log should be caught if it is an expected error, so that users are not left thinking Jenkins failed unexpectedly. Errr log: INFO: TEST #1 aborted java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Native Method) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Launcher$ProcStarter.join(Launcher.java:336) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459) at hudson.model.Run.run(Run.java:1376) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)
    via by pixman20,
  • Usage of PuTTY in command line from Hudson
    via Super User by kij
    ,
    • java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Native Method) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,