This page describes how to set Java properties and options on startup for JIRA Standalone and WAR distributions.

On this page:

Linux

  1. From <jira-install>/bin (Standalone) or <Tomcat-home>/bin (WAR installation), open setenv.sh.
  2. Find the section JVM_SUPPORT_RECOMMENDED_ARGS=
  3. Refer to the list of parameters below.

(info) Add all parameters in a space-separated list, inside the quotations.

Windows (starting from .bat file)

  1. From <jira-install>/bin (Standalone) or <Tomcat-home>/bin (WAR installation), open setenv.bat.
  2. Find the section set JVM_SUPPORT_RECOMMENDED_ARGS=
  3. Refer to the list of parameters below.

(info) Add all parameters in a space-separated list, inside the quotations.

Windows Service

There are two ways to configure system properties when starting Running JIRA Standalone as a Service, either via command line or in the Windows Registry

Setting Properties for Windows Services via Command Line

  1. Identify the name of the service that JIRA is installed as in Windows ( Control Panel > Administrative Tools > Services ):

    (info) In the above example, the SERVICENAME is: JIRA030908110721
  2. Open the command window from Start >> Run >> type in 'cmd' >> Enter
  3. cd to the bin directory of your JIRA Standalone instance, or the bin directory of your Tomcat installation if your are running JIRA WAR.
  4. Run:
    tomcat6w //ES//%SERVICENAME%
    
    .
    (info) In the above example, it would be tomcat6w //ES//JIRA030908110721
  5. Click on the Java tab to see the list of current start-up options:
  6. Append any new option on its own new line by adding to the end of the existing Java Options. Refer to the list of parameters below.

Setting Properties for Windows Services via the Windows Registry

In some versions of Windows, there is no option to add Java variables to the service. In these cases, you must add the properties by viewing the option list in the registry.

  1. Go to {{Start >> Run, and run "regedit32.exe".
  2. Find the Services entry:
    32-bit: HKEY_LOCAL_MACHINE >> SOFTWARE >> Apache Software Foundation >> Procrun 2.0 >> JIRA
    64-bit: HKEY_LOCAL_MACHINE >> SOFTWARE >> Wow6432Node >> Apache Software Foundation >> Procrun 2.0 >> JIRA
  3. To change existing properties, especially increasing Xmx memory, double-click the appropriate value.
  4. To change additional properties, double-click options.
  5. Refer to the list of parameters below. Enter each on a separate line.

Verifying Your Settings

To verify what settings are in place, check the <jira-home>/logs/atlassian-jira.log or catalina.out file. A section in the startup appears like this:

JVM Input Arguments : -Djava.util.logging.config.file=/usr/local/jira/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx384m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/local/jira/endorsed -Dcatalina.base=/usr/local/jira -Dcatalina.home=/usr/local/jira -Djava.io.tmpdir=/usr/local/jira/temp

This display is also available by Viewing your System Information.