Jira fails to start after upgrading to the 8.20+ version due to unrecognized parameters in the JVM
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
After upgrading from the 8.16.1 to 8.21.1 version, Jira failed to start, and the following errors have been observed:
In the C:\Program Files\Atlassian\JIRA\logs\commons-daemon.2022-01-10.log:
[2022-01-10 11:40:43] [error] [ 1004] CreateJavaVM Failed with error [-6]
[2022-01-10 11:40:43] [error] [ 1004] The system cannot find the file specified.
[2022-01-10 11:40:43] [error] [12148] Failed to start Java
[2022-01-10 11:40:43] [error] [12148] ServiceStart returned 4.In the C:\Program Files\Atlassian\Application Data\JIRAData\log\atlassian-jira.log:
2022-01-08 06:01:00,160-0500 Caesium-1-4 ERROR ServiceRunner [c.a.s.caesium.impl.SchedulerQueueWorker] Unhandled exception thrown by job QueuedJob[jobId=com.atlassian.analytics.client.upload.RemoteFilterRead:job,deadline=1641639660000]
javax.xml.stream.FactoryConfigurationError: Provider for class javax.xml.stream.XMLInputFactory cannot be createdEnvironment
Jira Server/Data Center 8.20+
Cause
Starting in Jira Software version 8.20, the installer comes bundled with a newer Java version. This typically suggests that prior to the upgrade, your Jira instance had some Java logging parameters enabled that are no longer supported with this newer application version and could be avoiding the JVM from starting up accordingly. You can refer to the page: Bundled Tomcat and Java versions for details.
Solution
You can tell the JVM to ignore unrecognized parameters during the startup by adding the following the steps outlined below:
1. Stop Jira;
2. Add the following parameter to the JVM options:
-XX:+IgnoreUnrecognizedVMOptionsThis parameter allows the JVM to ignore unrecognized top-level options. You can find the steps to include this parameter according to your operating system outlined in the article: Setting properties and options on startup
3. Start Jira;
Was this helpful?