XML restoration failed as Jira is unable to clean the cache directory

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

Summary

XML restoration failing with following exception:

2020-12-23 09:36:47,570+0700 JiraImportTaskExecutionThread-1 ERROR admin 572x450x1 abcd11 10.0.0.1 /secure/admin/XmlRestore.jspa [c.a.jira.plugin.PluginPath$JiraHomeAdapter] Unable to delete file: C:\Program Files\Atlassian\Application Data\Jira\plugins\.osgi-plugins\felix\felix-cache\bundle251\version0.0\plugin_5966330075261996795_eazybi-jira-6.1.2_1608690614195.jar-lib\0\META-INF\rails.root\vendor\gems\mondrian-olap\lib\mondrian\jars\olap4j-1.2.0.jar  exists:true  canRead:true  canWrite:true  isDirectory:false
2020-12-23 09:36:47,571+0700 JiraImportTaskExecutionThread-1 ERROR admin 572x450x1 abcd11 10.0.0.1 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Unable to clean the cache directory: C:\Program Files\Atlassian\Application Data\Jira\plugins\.osgi-plugins\felix
com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: C:\Program Files\Atlassian\Application Data\Jira\plugins\.osgi-plugins\felix
...
Caused by: java.io.IOException: Unable to delete file: C:\Program Files\Atlassian\Application Data\Jira\plugins\.osgi-plugins\felix\felix-cache\bundle251\version0.0\plugin_5966330075261996795_eazybi-jira-6.1.2_1608690614195.jar-lib\0\META-INF\rails.root\vendor\gems\mondrian-olap\lib\mondrian\jars\olap4j-1.2.0.jar

Environment

  • Jira 8.13.0
  • Jira Service Management 4.13.0
  • eazyBI Reports and Charts 6.1.2

Diagnosis

XML restoration failed despite assuring that Jira user has privileges to the Jira Home directory and re-built the .osgi-plugins directory.

The exception is specific to eazyBI JAR extractions and XML restoration works accordingly as we uninstall the app from the Jira instance.


Cause

eazyBI Support has confirmed that issue is reproducible on their end and they have a development ticket opened to address this in future versions of eazyBI app.

Solution

As a workaround, disable eazyBI app before XML restoration is performed and enable it back after the restoration.


Last modified on Jan 6, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.