要約

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 created

環境

Jira Server/Data Center 8.20+

原因

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.

ソリューション

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:+IgnoreUnrecognizedVMOptions

This 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;