-
Bug
-
Resolution: Fixed
-
Highest (View bug fix roadmap)
-
9.2.0, 9.7.1, 9.4.6, 9.8.1, 9.4.7, 9.4.9, 9.4.11
-
9.02
-
43
-
Severity 3 - Minor
-
226
-
-
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
[JRASERVER-74536] NullPointerException occurred while execution of workflows cleaning service
- The workaround provided, does not suppress or elminate the error from the logs. In order to eliminate this, a fix has been provided at Jira version 9.11, so you would need to schedule a upgrade to that version in order to completely fix this.
- A fix for this BUG for the 9.4 LTS versions is still not being planned on the roadmap as I've just checked internally. When a fix for the LTS version is available, it will be updated on this BUG ticket.
As noted by many others, the workaround does not work. Please would someone correct that information
Still issue on JSW 9.9.1 and jirahome/export/workflowexports is empty
Seeing it on v9.4.8 even when the workflow export directory <jirahome>/export/workflowexports is empty.
I have it also in 9.4.7 LTS and my workflowexports folder is empty
Not sure if this is linked but after fresh upgrade, I can't reindex my issues
The recommended workaround is useless: The error is thrown even when the workflow export directory <jirahome>/export/workflowexports is empty.
Dear Customers,
Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog.
The workaround for this bug is as follows: same as in the issue description
manually clear the workflow export directory (jirahome/export/workflowexports).
Please continue watching this ticket for future updates and changes in the timeline that impacts your work.
Best regards
Daniel Ramotowski
Software Engineer