Plugin removed and JIRA locked

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 has beeen upgraded (or a new version of a plugin installed) and JIRA throws a fatal error on restart.

The following appears in the atlassian-jira.log:

1 2 3 2011-08-12 10:34:54,220 main INFO [atlassian.plugin.manager.DefaultPluginManager] Plugin com.iamhuy.jira.plugin.issue-alternative-assignee was marked to be removed on restart. Removing now. 2011-08-12 10:34:54,221 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Removed plugin com.iamhuy.jira.plugin.issue-alternative-assignee 2011-08-12 10:34:58,277 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.

Cause

Two versions of the plugin have been installed:

  • The Version 1 plugin is in the $JIRA_INSTALL/atlassian-jira/WEB-INF/lib/ folder.

  • The Version 2 plugin (newer) is in the $JIRA_HOME/plugins/installed-plugins/ folder.

Resolution

  1. Shut down JIRA if it's still running.

  2. Look in the Version 1 directory ($JIRA_INSTALL/atlassian-jira/WEB-INF/lib/) and find any plugins that match, or are similar to, plugins listed in $JIRA_HOME/plugins/installed-plugins/

  3. Remove the matching or similar plugins and restart JIRA.

  4. Repeat until JIRA starts without errors.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.