JIRA Restart after restoring data throws "java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter"

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

Summary

Problem

JIRA becomes unaccessible (blank page) upon restart after restoring data. The following is thrown in atlassian-jira.log

1 2 3 4 5 2016-01-04 08:48:05,019 localhost-startStop-1 ERROR [c.a.jira.upgrade.UpgradeLauncher] An Error occurred during UpgradeLauncher servlet context initialisation - javax/xml/bind/DatatypeConverter. java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at com.atlassian.dbexporter.node.stax.StaxStreamWriter$1.setContentAsBinary(StaxStreamWriter.java:108) at com.atlassian.dbexporter.node.NodeBackup$RowDataNode.append(NodeBackup.java:238) at com.atlassian.dbexporter.exporter.DataExporter.exportRow(DataExporter.java:171)

Diagnosis

The instance is running into an issue handling binary data. The next step is to see which table that has column with Binary datatype, in this case, it's BLOB datatype.

Cause

An AO table has column with BLOB datatype. According to this documentation Developing your plugin with Active Objects, JIRA does not fully support BLOB datatype in AO.

Solution

Resolution

  • Shutdown JIRA

  • Find the plugin that has BLOB datatype

  • Remove the plugin from the $JIRA_HOME/plugins/installed-plugins

  • Restart JIRA

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.