Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70241

CustomisationsCheckScheduler:job failed due to binary incompatibilities

    XMLWordPrintable

Details

    Description

      Issue Summary

      Scheduler from ATST app com.atlassian.troubleshooting.jira.scheduler.CustomisationsCheckScheduler:job failed due to binary incompatibilities.

      The effect of this bug is that some information about changed files is not presented to the user when upgrading Jira. It does not cause any problems during normal operation or upgrade.

      Environment

      • Jira 7.x

      Steps to Reproduce

      1. Stop jira
      2. Install ATST App version 1.20.3 from https://marketplace.atlassian.com/apps/1217696/troubleshooting-and-support-jira/version-history
      3. Start Jira
      4. The error is raised, see below

      Expected Results

      No error is raised

      Actual Results

      The below exception is thrown in the log file:

      Caesium-1-3 ERROR ServiceRunner [c.a.scheduler.core.JobLauncher] Scheduled job with ID 'com.atlassian.troubleshooting.jira.scheduler.CustomisationsCheckScheduler:job' failed due to binary incompatibilities
      java.lang.NoSuchMethodError: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;
      at com.atlassian.troubleshooting.jira.pup.BaselineHashesService$MultiHashAccessor.lambda$new$2(BaselineHashesService.java:72)
      at java.util.Optional.ifPresent(Optional.java:159)
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Activity

          People

            Unassigned Unassigned
            tferreira@atlassian.com Tiago Ferreira (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: