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

XML Restore Fails if entities.xml is renamed

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      If the entities.xml file is renamed, JIRA should be able to recognise this and still parse the file. In support, anonymised backups are requested often from customers. Anonymising the data also renames the file in the backup zip. Supporter engineers are required to unzip, rename, then rezip the file before the backup file can be restored. The following error is throw in the logs if a incorrectly named file is restored:

      2013-02-25 17:32:30,163 JiraImportTaskExecutionThread-1 ERROR admin 1052x247x1 1fzoff1 0:0:0:0:0:0:0:1%0 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Error importing from zip file: "/Users/cshim/userdata/jira.5.2.5/jira/jirahome/import/rename.zip"
      java.io.IOException: Unable to find JIRA backup (entities.xml) inside of zip file: /Users/cshim/userdata/jira.5.2.5/jira/jirahome/import/rename.zip
      	at com.atlassian.jira.util.xml.JiraFileInputStream.getFileInputStream(JiraFileInputStream.java:137)
      	at com.atlassian.jira.util.xml.JiraFileInputStream.getBOMType(JiraFileInputStream.java:179)
      	at com.atlassian.jira.util.xml.JiraFileInputStream.<init>(JiraFileInputStream.java:54)
      	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.getInputSource(DefaultDataImportService.java:873)
      	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.parseXmlAndValidateBackupData(DefaultDataImportService.java:279)
      	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.doImport(DefaultDataImportService.java:229)
      	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:65)
      	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:28)
      	at com.atlassian.jira.task.ImportTaskManagerImpl$TaskCallableDecorator.call(ImportTaskManagerImpl.java:147)
      	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
      	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      	at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
      	at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      	at java.lang.Thread.run(Thread.java:680)
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cshim ChrisA
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: