java.lang.RuntimeException

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.

  • Finding more information on a Jenkins error
    via Stack Overflow by Sean Long
    ,
  • GitHub comment 18980#174621206
    via GitHub by lavalamp
    ,
  • GitHub comment 24267#210178583
    via GitHub by lavalamp
    ,
  • Hi, I've recently updated Jenkins to 2.9 (from 2.6), including all slave.jars and all plugins with their most recent versions. All of suddenly, job started at one particular slave hangs at xunit processing, which worked OK so far. This is what I see in job console: ... Build step 'Conditional steps (multiple)' marked build as failure Archiving artifacts \[xUnit\] \[INFO\] - Starting to record. \[xUnit\] \[INFO\] - Processing Custom Tool \[xUnit\] \[INFO\] - \[Custom Tool\] - 1 test report file(s) were found with the pattern 'Reports\unpacked\*_build-5481.rxlog.data' relative to 'c:\Jenkins\workspace\SecurexMonitoring' for the testing framework 'Custom Tool'. From time to time, the xunit processing finishes after unusually long period of time. But in most cases, I need to kill the job manually, because it blocks other jobs. Virtually the same works fine on two other slave machines. The only difference between the slaves is that the not-working one is located in different data center. But it was there also before. The response time of the problematic slave is around 150ms, so it should not be an issue either? Jenkins configuration should be the same on all three slaves. Once I kill the 'hanged' job, it throws this exception to master console: Jun 14, 2016 12:45:27 PM WARNING hudson.model.AbstractBuild$AbstractBuildExecution reportError Step ‘Publish xUnit test result report’ aborted due to exception: 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:1007) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:145) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:88) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:142) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Any idea what could be the cause of this problem or what to try to fix it? Feel free to let me know if you need more details. PS: added slave thread dump
    via by Pavel Kudrys,
  • Hi, I've recently updated Jenkins to 2.9 (from 2.6), including all slave.jars and all plugins with their most recent versions. All of suddenly, job started at one particular slave hangs at xunit processing, which worked OK so far. This is what I see in job console: ... Build step 'Conditional steps (multiple)' marked build as failure Archiving artifacts \[xUnit\] \[INFO\] - Starting to record. \[xUnit\] \[INFO\] - Processing Custom Tool \[xUnit\] \[INFO\] - \[Custom Tool\] - 1 test report file(s) were found with the pattern 'Reports\unpacked\*_build-5481.rxlog.data' relative to 'c:\Jenkins\workspace\SecurexMonitoring' for the testing framework 'Custom Tool'. From time to time, the xunit processing finishes after unusually long period of time. But in most cases, I need to kill the job manually, because it blocks other jobs. Virtually the same works fine on two other slave machines. The only difference between the slaves is that the not-working one is located in different data center. But it was there also before. The response time of the problematic slave is around 150ms, so it should not be an issue either? Jenkins configuration should be the same on all three slaves. Once I kill the 'hanged' job, it throws this exception to master console: Jun 14, 2016 12:45:27 PM WARNING hudson.model.AbstractBuild$AbstractBuildExecution reportError Step ‘Publish xUnit test result report’ aborted due to exception: 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:1007) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:145) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:88) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:142) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Any idea what could be the cause of this problem or what to try to fix it? Feel free to let me know if you need more details. PS: added slave thread dump
    via by Pavel Kudrys,
  • [JIRA] (JENKINS-24449) slave cleanup causes jobs to hang
    via by john.c.r...@gmail.com (JIRA),
  • Hello, I have recently started using the Amazon EC2 plugin to bring up Jenkins build slaves on demand. They are all created from the same AMI and set to shut down instead of terminate. The transition went very smoothly (as soon as the AMI had everything that was needed) however two of our builds are now misbehaving every single time. I've been able to find some very old slightly similar issues in Jira and Stackoverflow but nothing identical (and nothing using recent version of Jenkins). I am not 100% convinced the EC2 plugin has anything to do with this however this is when the problem started exhibiting. I've managed to narrow this issue to the 'Clean up unused Subversion modules' option in 'Build environment'. Whenever the build starts (either by SCM poll trigger or manually triggerred), the SCM checkout happens successfully (this is regardless of there being changes) and after the 'At revision xxx' message is printed out in the log, nothing happens anymore (no matter how long the job is left running) apart from the spinning circle. I have discovered that hitting the cancel button when in the console log page (top right next to the progress bar) will display a stacktrace in the build but the build will continue happily afterwards. Here's the stacktrace: {noformat} 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:1007) at hudson.FilePath.act(FilePath.java:996) at hudson.FilePath.isDirectory(FilePath.java:1532) at jenkins.plugins.workspace_cleaner.FilePathAdapter.isDirectory(FilePathAdapter.java:52) at jenkins.plugins.workspace_cleaner.ModuleCleaner.getSvnModulesIn(ModuleCleaner.java:59) at jenkins.plugins.workspace_cleaner.ModuleCleaner.getSvnModulesIn(ModuleCleaner.java:60) at jenkins.plugins.workspace_cleaner.ModuleCleaner.getSvnModulesIn(ModuleCleaner.java:60) at jenkins.plugins.workspace_cleaner.ModuleCleaner.getSvnModulesInFileSystem(ModuleCleaner.java:43) at jenkins.plugins.workspace_cleaner.ModuleCleaner.removeUnconfiguredModules(ModuleCleaner.java:21) at jenkins.plugins.workspace_cleaner.JenkinsGlue.setUp(JenkinsGlue.java:32) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1720) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) {noformat} I've worked around this by disabling this option. Let me know if I can provide any more info that could help.
    via by Simon Szumyłowicz,
    • java.lang.RuntimeException: java.lang.InterruptedException at hudson.plugins.tfs.model.Server.execute(Server.java:157) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:272) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:268) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:284) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:311) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:260) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 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.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.plugins.tfs.model.Server.execute(Server.java:153) ... 13 more

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Pawan
    3 times, last one,
    35 more bugmates