Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-45917

XML backup or restore of AO tables fails to complete due to Jira running out of heap space




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


      As part of JIRA Service Desk now, JIRA is storing the incoming mails in the database (done by the JEPP). Those are stored inside the AO_2C4E5C_MAILITEMCHUNK table.

      JIRA is, sometimes, silently failing to import or export the active objects part of the backup.

      Steps to Reproduce

      1. Install JIRA;
      2. Import the backup linked on the private comments.
      3. JIRA will stop importing once it reaches 90%. Restart JIRA.
      4. Navigate to Administration » System » Plugin Data Storage and verify what has been imported.

      Expected Results

      All entries in the active objects table would have been imported/exported.

      Actual Results

      • Exporting: JIRA creates the backup normally, but upon inspecting the activeobjects.xml file (using the grep below) not all entries are in the file.
      • Importing: JIRA fails to import the data once it reaches 90%, but after restarting JIRA it seems to have imported correctly. Inspecting the Plugin Data Storage shows most tables as empty, and inspecting the activeobjects file shows all data.

      The following errors might be found in the Jira logs:
      The following errors might be seen in the logs:

      2020-11-06 19:19:32,337-0500 JiraImportTaskExecutionThread-1 ERROR anonymous 528x1190x1 409hrc XX.XX.XX.XXX /secure/SetupImport.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.OutOfMemoryError
      	at java.lang.AbstractStringBuilder.hugeCapacity(AbstractStringBuilder.java:161)
      	at java.lang.AbstractStringBuilder.newCapacity(AbstractStringBuilder.java:155)
      	at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:125)
      	at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
      	at java.lang.StringBuilder.append(StringBuilder.java:136)
      	at java.lang.StringBuilder.append(StringBuilder.java:76)
      [2020-08-20 01:00:16,045-0400 JiraImportTaskExecutionThread-1 ERROR test 1002x937x1 1fztp06 XXXXXXXXX /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.OutOfMemoryError020-08-20 01:00:16,045-0400 JiraImportTaskExecutionThread-1 ERROR test 1002x937x1 test XXXXXX /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.OutOfMemoryErrorjava.lang.OutOfMemoryError)
      2019-03-18 07:36:01,857 JiraImportTaskExecutionThread-1 ERROR test 381x754x1 1py7sdr XXXXXXXX /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.OutOfMemoryError: Java heap space
      java.lang.OutOfMemoryError: Java heap space

      This seems to be happening because JIRA runs out of memory due to import, but fails to log any errors or warnings.


      To verify the data inside the activeobjects.xml backup, run:

      grep -E  "data tableName=|<row>" activeobjects.xml | uniq -c

      This will show how many rows were exported for each table. For example, when JIRA failed to export correctly, this was shown:

            1   <data tableName="AO_21D670_WHITELIST_RULES">
            3     <row>
            1   <data tableName="AO_2C4E5C_MAILCHANNEL">
            1     <row>
            1   <data tableName="AO_2C4E5C_MAILCONNECTION">
            1     <row>
            1   <data tableName="AO_2C4E5C_MAILGLOBALHANDLER">
            1   <data tableName="AO_2C4E5C_MAILHANDLER">
            5     <row>
            1   <data tableName="AO_2C4E5C_MAILITEM">
         3625     <row>
            1   <data tableName="AO_2C4E5C_MAILITEMAUDIT">
         3625     <row>
            1   <data tableName="AO_2C4E5C_MAILITEMCHUNK">
          691     <row>

      It is possible to see what tables were (supposed to be) exported to the backup with:

      grep "table name=" activeobjects.xml


      Follow our Increasing JIRA Memory guide to increase the memory available to JIRA, restart JIRA and try to import/export the backup again. If this doesn't work, please follow the instructions below:

      For importing:
      It is possible to remove the affected lines from the backup with:

      1. Run:
        grep -En  "data tableName=" activeobjects.xml | grep -A1 "MAILITEMCHUNK" | cut -d":" -f1

        This will return two numbers.

      2. use vim to open the activeobjects.xml and run:

        Where num1 and num2 are the numbers returned in the first step. e.g.:

      3. save and exit vim;
      4. zip the backup again and import.

      This will return the body of the emails that are stored.

      To export:

      1. Turn off the Email Puller so that no new mail will be added to the database
        • JIRA Administration > System > Global Mail Settings
      2. Wait at least 5 minutes so that the mail processor is able to process mail that is already in the database
      3. Stop JIRA;
      4. Run the following update in the database to delete the mail items:
        • Optional: backup this table using your database's native tools before running the update
      5. Restart JIRA;
      6. Export the data again.
      7. Turn the Email Puller back on


        Issue Links



              sseaver Shaun S
              mfernandes@atlassian.com Matheus Fernandes
              28 Vote for this issue
              45 Start watching this issue