Issue Summary

Personal Access Tokens (PATs) were introduced in Jira DC version 8.14.  Here is the guide to using them:

• Using Personal Access Tokens

In the section "Limit token creation", you can expand a list of limits you can set on the PATs.  These limitations are enacted by adding JVM arguments as listed in Setting properties and options on startup.  However, when these JVM arguments are added to the Java options for a Windows service, Jira will fail to start.  Jira will start if they are added to Java 9 options. 

Steps to Reproduce

1. Add the option "-atlassian.pats.max.tokens.expiry.days=30" to the JVM args in the Windows service. 
2. Jira fails to start. 

Expected Results

Jira will start and respect the additional PAT argument. 

Actual Results

Jira fails to start and the following is found in the commons-daemon log:

[2021-03-23 13:42:57] [info] [ 7624] Apache Commons Daemon procrun (1.2.3.0 64-bit) started.
[2021-03-23 13:42:57] [info] [ 7624] Running Service 'JIRASoftware190917125414'...
[2021-03-23 13:42:57] [info] [ 6760] Starting service...
[2021-03-23 13:42:57] [error] [ 5212] CreateJavaVM Failed with error [-1]
[2021-03-23 13:42:57] [error] [ 5212] The system could not find the environment option that was entered.
[2021-03-23 13:42:57] [error] [ 6760] Failed to start Java
[2021-03-23 13:42:57] [error] [ 6760] ServiceStart returned 4.
[2021-03-23 13:42:57] [info] [ 7624] Run service finished.
[2021-03-23 13:42:57] [info] [ 7624] Apache Commons Daemon procrun finished.

The following is found in the stderr log:

2021-03-23 13:42:57 Apache Commons Daemon procrun stderr initialized.
Unrecognized option: -atlassian.pats.max.tokens.expiry.days=30

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available