Can't enable Jira Data Center plugins
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
The steps apply to the following Jira Data Center environments
Jira 7.x, Jira 8.x, Jira 9.x, Jira 10.x, Jira 11.x
Jira Data Center typically doesn’t need the plugins cache cleared. In this page, we discuss when it makes sense to perform this operation and how to do it.
How the plugin cache works
Jira Data Center uses several internal directories to support plugin operation. Under normal conditions, there is no need to manipulate these - the application manages them.
However, there may be situations that require manual clearing. You can detect these situations in the logs by observing .jar file issues, causing Java dependency errors on plugin load (ClassNotFoundException, MethodNotFoundException, ClassCastException and so on).
Directory | Explanation |
|---|---|
| Contains the following subdirectories: 1. 2. |
| Used by Tomcat for runtime JSP compilation (disabled in Jira 10 and above) |
| The JVM’s general temporary directory, |
.bundled-plugins is a historic directory and is not used in supported versions..osgi-plugins is only read from the local home, not the shared home.
Clearing these directories is not a definitive solution to most problems. However, it may form part of the troubleshooting steps to eliminate unknown problems with cached content.
In most situations, clearing the plugin cache doesn’t add anything to a regular restart. Jira admins often do this when restarting in troubleshooting contexts to use the restart to also rule out a corrupted cache, even if unlikely.
Solution
Stop the Jira service on a node
Delete the contents of the following directories:
JIRA_HOME/plugins/.osgi-pluginsJIRA_INSTALL/work(if Jira 9 or earlier)JIRA_INSTALL/temp
Start Jira. The cleared directories will repopulate over time
If you have more nodes in your cluster, repeat steps 1 to 3 for the remaining nodes
Customers using Docker or Kubernetes
It might be difficult to access LOCAL_HOME when the container is stopped. To work around that, you can set the ATL_JIRA_CLEAR_PLUGIN_CACHE environment variable to request that the container clear the cache before the application starts. For more information, see the article How to Clear Jira's Plugin Cache in a Kubernetes Helm Chart Installation
If you continue to have problems starting Jira, consider reviewing the article Jira Data Center startup fails with a message that required plugins are not started or contacting Atlassian Support
Related Articles
Was this helpful?