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

NullPointerException occurred while execution of workflows cleaning service

    XMLWordPrintable

Details

    • 9.02
    • 43
    • Severity 3 - Minor
    • 226
    • Hide
      Atlassian Update – 29 June 2023

      Dear Customers,
      We're happy to announce that this issue is fixed in 9.11.0 release.

      Best regards
      Jakub Sildatk
      Jira DC Software Engineer

      Show
      Atlassian Update – 29 June 2023 Dear Customers, We're happy to announce that this issue is fixed in 9.11.0 release. Best regards Jakub Sildatk Jira DC Software Engineer

    Description

      Problem

      Errors in logs about service cleaning workflows
      Caesium-1-4 ERROR anonymous [c.a.j.p.w.sharing.file.FileCleaningJobSchedulerImpl$FileCleaningJob] Error occurred while cleaning workflow exports..

      This is the only area affected by the bug. It does not affect the export process itself or any other part of Jira.

      Environment

      Jira Software DC 9.2.0
      Jira Software Server 9.2.0

      Steps to Reproduce

      Install a fresh instance of Jira Software 9.2.0 or higher and wait for the service to run (by default it runs every 1h).

      Expected Results

      The file cleaning service should run and clear the workflow export files from jirahome/export/workflowexports with no errors logged in application logs.

      Actual Results

      The file cleaning service fails to clear the files from the location and it logs an exception similar to the one below:

      2022-10-03 21:23:34,001+0000 Caesium-1-4 ERROR anonymous [c.a.j.p.w.sharing.file.FileCleaningJobSchedulerImpl$FileCleaningJob] Error occurred while cleaning workflow exports.
      java.lang.NullPointerException
      at com.atlassian.jira.plugins.workflow.sharing.file.FileCleaningJobSchedulerImpl$FileCleaningJob.execute(FileCleaningJobSchedulerImpl.java:94)
      at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:110)
      at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:80)
      at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
      at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
      at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
      at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
      at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:402)
      at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:380)
      at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
      at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
      at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
      at java.lang.Thread.run(Thread.java:745)
      

      Workaround

      • manually clear the workflow export directory (jirahome/export/workflowexports).
      • The workaround provided, does not suppress or elminate the error from the logs. In order to eliminate this, upgrade Jira to one of the Fixed Versions to completely fix this.

      Notes

      It does not reproduce on 9.1.0 or 8.20.0 so it looks this was introduced in 9.2.0

      Attachments

        Issue Links

          Activity

            People

              9e3a0496a19c Jakub Sildatk
              5b97fcabbfc1 Diego Moreno
              Votes:
              44 Vote for this issue
              Watchers:
              68 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: