Setting Java parameters for Windows Service is causing Startup problems or not being recognized

Still need help?

The Atlassian Community is here for you.

Ask the community

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:

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.decodeparameters

However 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:

java.awt.headless : true -Datlassian.standalone=JIRA -Dmail.mime.decodeparameters=true

Diagnosis

JIRA is running as a Windows Service.

Cause

The Java parameters are not being properly parsed.

Resolution

  1. Bring up the Windows Service properties, as from our Setting Properties and Options on Startup documentation.
  2. Check the Startup parameters for the following:

    1. Ensure that each defined parameter is defined on its own line.
    2. Ensure that there are no extra spaces at the end of the parameters.
  3. Restart JIRA.

(warning) Highlighting your list helps, as in the below example:

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.