java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V

Jenkins JIRA | Johan Cronje | 3 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    When we upgraded from 1.545 to 1.549, we found that we could no longer launch our Windows slaves using the 'DCOM' method. Unfortunately we cannot use JNLP because these are libvirt slaves, and choosing JNLP causes the instances to not even start up (due to issues like JENKINS-8004). What is happening is this: # libvirt starts the slave # Jenkins logs in to the slave # It then tries to query the Java version #* ... and it all goes pear-shaped from here. The stack trace is: {noformat}Error while launching <instance> on Hypervisor qemu+ssh://root@node2:22/system?no_verify=1&no_tty=1. java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.openForRead(WindowsRemoteProcessLauncher.java:282) at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.launch(WindowsRemoteProcessLauncher.java:140) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:233) at hudson.plugins.libvirt.VirtualMachineLauncher.launch(VirtualMachineLauncher.java:136) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) 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:744){noformat} So it seems as though the jcifs used is maybe the wrong version (I see that it was patched some time in 2011 to include the 'setTimeout' function). Maybe it was reverted/removed? What could be the cause of this?

    Jenkins JIRA | 3 years ago | Johan Cronje
    java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V
  2. 0

    When we upgraded from 1.545 to 1.549, we found that we could no longer launch our Windows slaves using the 'DCOM' method. Unfortunately we cannot use JNLP because these are libvirt slaves, and choosing JNLP causes the instances to not even start up (due to issues like JENKINS-8004). What is happening is this: # libvirt starts the slave # Jenkins logs in to the slave # It then tries to query the Java version #* ... and it all goes pear-shaped from here. The stack trace is: {noformat}Error while launching <instance> on Hypervisor qemu+ssh://root@node2:22/system?no_verify=1&no_tty=1. java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.openForRead(WindowsRemoteProcessLauncher.java:282) at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.launch(WindowsRemoteProcessLauncher.java:140) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:233) at hudson.plugins.libvirt.VirtualMachineLauncher.launch(VirtualMachineLauncher.java:136) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) 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:744){noformat} So it seems as though the jcifs used is maybe the wrong version (I see that it was patched some time in 2011 to include the 'setTimeout' function). Maybe it was reverted/removed? What could be the cause of this?

    Jenkins JIRA | 3 years ago | Johan Cronje
    java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V
  3. 0

    This is due to an incorrect build of the 2.1 jar file. h3. Impacts This affects 6.3-OD1 (released on 31 Mar 2014). It affects GitHub synchronization where there's at least one PR. h3. Cause It is causing the wrong egit {{PullRequest}} class to be loaded into the jar in the original 2.1 jar file uploaded to maven.atlassian.com. The DVCS Connector has its own copy of egit {{PullRequest}} class but it's not properly included in the original 2.1 jar file. In original 2.1 jar file: {code} 2014-03-12 13:16:08 ..... 7489 2140 org/eclipse/egit/github/core/PullRequest.class {code} In the 2.1.3 jar file (with the correct {{PullRequest}} class): {code} 2012-12-03 17:10:00 ..... 7276 2062 org/eclipse/egit/github/core/PullRequest.class {code} This affected the 6.3 OD1 release, with the following errors when synchronizing GitHub requests: {quote} @40000000533ca2100c23c3e4 2014-04-03 10:49:26,200 pool-15-thread-1 ERROR nmason 649x480x1 esyrp 59.167.133.1,59.167.29.201 /rest/bitbucket/1.0/repository/12/fullsync [dvcs.service.message.MessageConsumer] org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d384 java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d76c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100c241204 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100c2415ec at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100c241dbc at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100c2421a4 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100c243144 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) @40000000533ca2100c24352c at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) @40000000533ca2100c24352c at java.lang.Thread.run(Thread.java:662) @40000000533ca2100d074614 Exception in thread "pool-15-thread-1" java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100d07c314 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100d07f1f4 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100d08539c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100d08633c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100d08b15c at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100d08e80c at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) @40000000533ca2100d095d3c at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) @40000000533ca2100d096124 at java.lang.Thread.run(Thread.java:662) {quote} We could not rebuild and redeploy a good version due to https://ecosystem.atlassian.net/browse/AMPS-1112

    Atlassian JIRA | 3 years ago | Zehua Liu [Atlassian]
    java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d76c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100c241204 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100c2415ec at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100c241dbc at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100c2421a4 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100c243144 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    This is due to an incorrect build of the 2.1 jar file. h3. Impacts This affects 6.3-OD1 (released on 31 Mar 2014). It affects GitHub synchronization where there's at least one PR. h3. Cause It is causing the wrong egit {{PullRequest}} class to be loaded into the jar in the original 2.1 jar file uploaded to maven.atlassian.com. The DVCS Connector has its own copy of egit {{PullRequest}} class but it's not properly included in the original 2.1 jar file. In original 2.1 jar file: {code} 2014-03-12 13:16:08 ..... 7489 2140 org/eclipse/egit/github/core/PullRequest.class {code} In the 2.1.3 jar file (with the correct {{PullRequest}} class): {code} 2012-12-03 17:10:00 ..... 7276 2062 org/eclipse/egit/github/core/PullRequest.class {code} This affected the 6.3 OD1 release, with the following errors when synchronizing GitHub requests: {quote} @40000000533ca2100c23c3e4 2014-04-03 10:49:26,200 pool-15-thread-1 ERROR nmason 649x480x1 esyrp 59.167.133.1,59.167.29.201 /rest/bitbucket/1.0/repository/12/fullsync [dvcs.service.message.MessageConsumer] org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d384 java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d76c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100c241204 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100c2415ec at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100c241dbc at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100c2421a4 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100c243144 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) @40000000533ca2100c24352c at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) @40000000533ca2100c24352c at java.lang.Thread.run(Thread.java:662) @40000000533ca2100d074614 Exception in thread "pool-15-thread-1" java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100d07c314 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100d07f1f4 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100d08539c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100d08633c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100d08b15c at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100d08e80c at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) @40000000533ca2100d095d3c at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) @40000000533ca2100d096124 at java.lang.Thread.run(Thread.java:662) {quote} We could not rebuild and redeploy a good version due to https://ecosystem.atlassian.net/browse/AMPS-1112

    Atlassian JIRA | 3 years ago | Zehua Liu [Atlassian]
    java.lang.NoSuchMethodError: org.eclipse.egit.github.core.PullRequest.getReviewComments()I @40000000533ca2100c23d76c at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.updateCommentsCount(GitHubPullRequestSynchronizeMessageConsumer.java:292) @40000000533ca2100c241204 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.processPullRequestComments(GitHubPullRequestSynchronizeMessageConsumer.java:242) @40000000533ca2100c2415ec at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:109) @40000000533ca2100c241dbc at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:40) @40000000533ca2100c2421a4 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.run(MessageExecutor.java:273) @40000000533ca2100c243144 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

    Root Cause Analysis

    1. java.lang.NoSuchMethodError

      jcifs.smb.SmbFileInputStream.setTimeout(J)V

      at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.openForRead()
    2. org.jvnet.hudson
      WindowsRemoteProcessLauncher.launch
      1. org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.openForRead(WindowsRemoteProcessLauncher.java:282)
      2. org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.launch(WindowsRemoteProcessLauncher.java:140)
      2 frames
    3. hudson.os.windows
      ManagedWindowsServiceLauncher.launch
      1. hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:233)
      1 frame
    4. hudson.plugins.libvirt
      VirtualMachineLauncher.launch
      1. hudson.plugins.libvirt.VirtualMachineLauncher.launch(VirtualMachineLauncher.java:136)
      1 frame
    5. Hudson
      SlaveComputer$1.call
      1. hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228)
      1 frame
    6. Java RT
      ThreadPoolExecutor$Worker.run
      1. java.util.concurrent.FutureTask.run(FutureTask.java:262)
      2. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      3. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      3 frames