Setting Java parameters for Windows Service is causing Startup problems or not being recognized
Platform Notice: Data Center Only - This article only applies to Atlassian products 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
Symptoms
Setting Java parameters for your Windows Service fails JIRA startup or is not recognised. For example, the following may appear in the atlassian-jira.log:
1
WARNING: The system property 'mail.mime.decodeparameters' is not set to true. This may result in e-mail attachments with non-Latin filenames being dropped. For more information please see https://confluence.atlassian.com/display/JIRA/__setting_mail.mime.decodeparametersHowever looking at the System Info we can see the parameter has been set:
Additionally, the parameter can be found within another parameter in the startup logs, as below:
1
java.awt.headless : true -Datlassian.standalone=JIRA -Dmail.mime.decodeparameters=trueDiagnosis
JIRA is running as a Windows Service.
Cause
The Java parameters are not being properly parsed.
Solution
Resolution
Bring up the Windows Service properties, as from our Setting Properties and Options on Startup documentation.
Check the Startup parameters for the following:
Ensure that each defined parameter is defined on its own line.
Ensure that there are no extra spaces at the end of the parameters.
Restart JIRA.
⚠️ Highlighting your list helps, as in the below example:
Was this helpful?