Recognized system properties for Jira applications

Setting properties and options on startup

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Jira supports some configuration and debugging settings that can be enabled through Java system properties. System properties are usually set by passing the -D flag to the Java virtual machine in which Jira is running. See Setting properties and options on startup.

List of startup parameters

Memory property


Related pages


These properties are pre-existing. See related pages for instructions.

Increasing Jira memory





-Xloggc:C:\Program Files\Atlassian\Application Data\JIRA\log\atlassian-jira-gc-%t.log




These properties are pre-existing, and are used for Garbage Collection tuning.

Using Garbage Collection Logs to Analyze Jira Application Performance
Analyze OutofMemory errors in Jira server with Heap Dumps


[Archived] Profiling Memory and CPU Usage with YourKit



These properties are pre-existing, and are used to configure the size of the JVM code cache. A high value of reserved size allows Jira to load more installed apps.

The default configuration should be optimal for most Jira instances and solve any problems with the code cache getting full.

KB article: Jira crashes due to the CodeCache

Mail property


Related pages


Set to 'true' to disable mail. In Linux, there is a pre-existing flag to uncomment.

Migrating Jira to another server
Notifications Are Issued for Incorrect Jira Issues


If set to "true", logs statements related to mail

Configuring Jira's SMTP mail server to send notifications
Creating issues and comments from email


Unable to Decode Mail Subject or Body when Creating Issue From Email


IMAP setup fails with AUTHENTICATE Failed error in logs in Jira server when using OAuth


Jira server unable to retrieve messages from IMAP server with No login methods supported error


Sets mail handler to work correctly with emails from RFC 2231-compliant mail clients.


Problems Sending Email from Jira - EHLO requires domain address

Encoding property


Related pages



Set to utf-8 for encoding consistency

Characters Not Supported by ASCII are Being Displayed as Question Marks
Internationalization and Encoding Troubleshooting
SQL Exception while updating issues or importing data in Jira applications with MySQL due to encoding
International Characters in Notification Email Subject Lines Are Being Replaced with Question Mark

Other Properties


Related pages


Incorrect Times Displayed in Jira


Values include Basic,Digest,Negotiate,NTLM

Jira Startup Fails Due to 'java.lang.SecurityException Unable to locate a login configuration'
Subversion Plugin Displays 'An unknown error occurred - actions == null' Due to SVN Authentication



(Archived) OutOfMemory Due to Tomcat Memory Leak


Enable/Disable assertions

java.lang.AssertionError When Sending Mail Via SMTP

SocketException to Announce 'Invalid argument' for an Available Port

Unable to Send Email '' Due to SMTP Server via SSL


Ships with true by default. Allows thumbnail generation.





Outbound Proxy Server hostname and portHow to Configure an Outbound HTTP and HTTPS Proxy for Jira applications
Logging into another Atlassian application logs me out of Confluence

Time Jira waits for apps to load.

Jira System Plugin Timeout While Waiting for Plugins to Enable

-Datlassian.plugins.startup.options="--disable-all-addons --disable-addons=com.atlassian.test.plugin"

Allows Jira to start with all user installed or specific user installed apps disabled. For more information on manual start up and specifying apps, see Start and Stop Jira applications.Start and Stop Jira applications

Hides the details of errors that are displayed after starting Jira. The page (johnson) where these are displayed will still notify you about the errors.


Disables the page (johnson) that displays errors after starting Jira if there are only dismissible warnings. The page will appear if there are any important errors.


This parameter allows to bypass any bad arguments being passed to Java.

Add the parameter at Jira startup to ensure that Jira won’t fail to start due to a bad parameter.

Auditing properties

These properties control the auditing feature, determining the number of audit entries logged, or stored in the database, and the size of those entries. Changing these settings will only affect new audit entries.

Increasing the amount of auditing done may have an adverse effect on performance.

Default valueDescription

Maximum number of concurrent non-freetext search requests allowed, defaults to 10 per node

Maximum number of concurrent freetext search requests allowed, defaults to 5 per node

Timeout in seconds for a queued search request, defaults to 30 seconds


Maximum number of audit event rows stored in DB, events exceeding the limit get deleted in time order, defaults to 10M checked on hourly basis


Buffer to accommodate new audit events, defaults to 1000 rows


maximum number of events to be deleted per database transaction used when enforcing retention limits, defaults to 10,000 rows


Database size check, running every 60 minutes

Maximum number of audit events written to system log file in case of error, defaults to 3


Database retention check, which deletes events exceeding retention period, running every 24 hours


Size limit in megabytes for individual audit file, file rotates when limit is reached, defaults to 100MB


Maximum number of audit files, the earliest file will be deleted when limit is reached, defaults to 100


Maximum number of audit events kept in buffer waiting to be consumed, defaults to 10,000

Maximum number of audit events dispatched to consumer, defaults to 3,000 per batch

How long the coverage cache is valid, defaults to 30 seconds

Custom fields

Default valueDescription

To decrease reindex time and improve overall performance, custom field values are fetched in batches of 50. This speeds up time-consuming operations such as database search. Currently the property works only with Jira built-in custom fields.

To disable the property, change the default to 1. Changing the property values, and getting the property to work for the first time requires full reindex.

Last modified on Apr 21, 2022

Was this helpful?

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