XML Backup export fails with javalangRuntimeException

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

Generating an XML back up fails with the following exception :

An exception occurred backing up: java.lang.RuntimeException: Could not get unique fields for table 'AO_E8B6CC_REPO_TO_CHANGESET&#39

The following appears in the atlassian-jira.log

2015-11-23 18:44:56,036 http-bio-8080-exec-3 ERROR jira_admin 1124x2164x1 122vam1 82.46.53.54,127.0.0.1 /secure/admin/XmlBackup.jspa [web.action.util.XmlBackup] Exception occurred backing up: java.lang.RuntimeException: Could not get unique fields for table 'AO_E8B6CC_REPO_TO_CHANGESET' java.lang.RuntimeException: Could not get unique fields for table 'AO_E8B6CC_REPO_TO_CHANGESET' at net.java.ao.schema.helper.DatabaseMetaDataReaderImpl.getUniqueFields(DatabaseMetaDataReaderImpl.java:209) at net.java.ao.schema.helper.DatabaseMetaDataReaderImpl.getFields(DatabaseMetaDataReaderImpl.java:79) at net.java.ao.schema.ddl.SchemaReader.readFields(SchemaReader.java:139) at net.java.ao.schema.ddl.SchemaReader.readTable(SchemaReader.java:122) at net.java.ao.schema.ddl.SchemaReader.access$000(SchemaReader.java:60) at net.java.ao.schema.ddl.SchemaReader$1.apply(SchemaReader.java:110) at net.java.ao.schema.ddl.SchemaReader$1.apply(SchemaReader.java:107) at com.google.common.collect.Iterators$8.next(Iterators.java:812) ... Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 1,954 milliseconds ago. The last packet sent successfully to the server was 1,952 milliseconds ago. at sun.reflect.GeneratedConstructorAccessor208.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3589) ... Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost. at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:3039) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3489) ... 223 more 2015-11-23 18:44:56,335 http-bio-8080-exec-3 ERROR jira_admin 1124x2164x1 122vam1 82.46.53.54,127.0.0.1 /secure/admin/XmlBackup.jspa [NoModule] There was an error getting a DBCP datasource. java.lang.RuntimeException: Unable to obtain a connection from the underlying connection pool at org.ofbiz.core.entity.jdbc.interceptors.connection.ConnectionTracker.trackConnection(ConnectionTracker.java:60) at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.trackConnection(DBCPConnectionFactory.java:243)

Cause

The table AO_E8B6CC_REPO_TO_CHANGESET which belongs to the JIRA DVCS Connector Plugin is corrupted.

Resolution

  1. Navigate to "Plugin Data Storage"

    1. This is located in JIRA Administration > System

    2. You can also use keyboard shortcuts, type g+g and search for "Plugin Data Storage"

  2. Make a list of the tables associated with the JIRA DVCS Connector Plugin. For example:

    AO_E8B6CC_ISSUE_TO_CHANGESET AO_E8B6CC_REPOSITORY_MAPPING AO_E8B6CC_CHANGESET_MAPPING AO_E8B6CC_ORGANIZATION_MAPPING AO_E8B6CC_REPO_TO_CHANGESET
  3. Backup your JIRA data before making any changes.

  4. Uninstall the JIRA DVCS Connector Plugin, dropping the associated tables from the database, and then re-install the plugin.

  5. Re-sync again (this may take a while)

Updated on May 22, 2025

Still need help?

The Atlassian Community is here for you.