-
Bug
-
Resolution: Fixed
-
Low
-
5.12.7
-
1
-
Severity 3 - Minor
-
Issue Summary
Though the assets import process runs fine, there are some issues observed in processing the results.
The import status shows as "OK," but the record is displayed under the "Running" section.
Due to this error, the imports would assume the end date of the next successful import run.
This is reproducible on Data Center: Yes
Steps to Reproduce
- We are not able to reproduce this issue, but customer faces this issue intermittently.
Expected Results
- The process results are published correctly, and the process results tab shows the correct status.
Actual Results
The below exception is thrown in the insight_import.log file:
2024-03-13 05:21:30,080+0000 insight-InsightThreadGroup-worker-thread-1814 WARN jiraadmin [c.r.j.p.i.s.imports.common.DefaultImportService] Unable to create progress result. null
2024-03-13 05:21:33,109+0000 insight-InsightThreadGroup-worker-thread-1814 ERROR jiraadmin [c.r.j.p.i.s.analytics.service.ImportExportAnalyticsServiceImpl] Could not publish import result analytics
java.lang.NullPointerException
at com.riadalabs.jira.plugins.insight.services.analytics.service.ImportExportAnalyticsServiceImpl.publishImportFinishedEvent(ImportExportAnalyticsServiceImpl.java:41)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.finishProgress(DefaultImportService.java:1733)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.doImportFromSource(DefaultImportService.java:873)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.lambda$_startImport$0(DefaultImportService.java:717)
at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
-
- Closed
-