Jira is not starting due to: Cannot load the application properties metadata file jpm.xml
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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 Jira instance doesn't start due to the error: Cannot load the application properties metadata file jpm.xml, and the symptoms in the following KBs have been discarded:
- Jira fails to start with DataAccessException: Cannot load the application properties metadata file
- Advanced Jira application configuration - The jpm.xml file You made sure you carried over any change made to this file just if Atlassian support recommended it. Otherwise, note that the
jpm.xmlfile should not be edited, as explained in the document. - Indexing fails due to a modified jpm.xml file
Environment
Any Jira version supported
Diagnosis
The following errors are shown in the atlassian-jira.log file during the Jira starting process:
___ Starting the JIRA Plugin System _________________
2023-01-01 00:00:00,000+0000 JIRA-Bootstrap ERROR [c.a.jira.startup.BootstrapContainerLauncher] A fatal error occurred during bootstrapping. JIRA has been locked.
io.atlassian.util.concurrent.LazyReference$InitializationException: io.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.jira.exception.DataAccessException: Cannot load the application properties metadata file jpm.xml
at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)
at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)
at io.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:95)
2023-01-01 00:00:00,000+0000 JIRA-Bootstrap ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@251434f6] from the invoker [com.atlassian.event.internal.ComparableListenerInvoker@7ff60f27]
java.lang.RuntimeException: io.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.jira.exception.DataAccessException: Cannot load the application properties metadata file jpm.xml. Listener: com.atlassian.jira.plugin.JiraOsgiContainerManager event: com.atlassian.plugin.event.events.PluginFrameworkStartingEvent
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:53) 2023-01-01 00:00:00,000+0000 JIRA-Bootstrap ERROR [c.a.plugin.loaders.SinglePluginLoader] Error loading plugin or descriptor: system-webresources-plugin.xml
java.lang.NullPointerException
at org.dom4j.io.DOMReader.createDocument(DOMReader.java:251)
at org.dom4j.io.DOMReader.read(DOMReader.java:74)
at com.atlassian.plugin.parsers.XmlDescriptorParser.createDocument(XmlDescriptorParser.java:106)
at com.atlassian.plugin.parsers.XmlDescriptorParser.<init>(XmlDescriptorParser.java:78)
at com.atlassian.plugin.parsers.XmlDescriptorParserFactory.getInstance(XmlDescriptorParserFacto2023-01-01 00:00:00,000+0000 http-nio-8081-exec-1 ERROR anonymous 000x0x0 - IP /rest/api/2/search [c.a.j.w.f.s.security.csp.DynamicContentSecurityPolicyResponseWrapperFactory] Failed to read property 'jira.security.csp.sandbox.excluded.content.type'. Check if jira.home is set.
io.atlassian.util.concurrent.LazyReference$InitializationException: io.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.jira.exception.DataAccessException: Cannot load the application properties metadata file jpm.xml
at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)
at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)
Cause
- The setenv.sh format is completely changed.
- Typos JVM parameters configured in the setenv.sh file.
- Unsupported JVM parameters configured in the setenv.sh file.
Solution
- Replace the current setenv.sh by the one shipped with the original Jira version.
- Look for any typo in the setenv.sh file and fix it.
- Manually configure your JVM properties as suggested in Setting properties and options on startup - Linux
Last modified on Sep 21, 2023
Powered by Confluence and Scroll Viewport.