JIRA Unable to Startup After Migration or Upgrade
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
Symptoms
Jira unable to startup.
The following appears in the atlassian-jira.log:
1
2
3
__ Plugin System Started _________________
2012-04-12 17:00:22,233 main ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Exception during consistency check: java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) previously initiated loading for a different type with name "javax/mail/Message"
java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) previously initiated loading for a different type with name "javax/mail/Message"Cause
Possibility caused by incompatibility plugins after upgrade or migrate to higher versions
Workaround
Go to this directory: $JIRA_HOME/plugins/installed-plugins
Remove or move the incompatible plugin that doesn't fit with the current JIRA version. You can check the compatibility list at Atlassian Plugins Exchange
Restart JIRA.
Was this helpful?