Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.
For long-term use, JIRA should be configured to automatically restart when the operating system restarts. For Windows servers, this means configuring JIRA to run as a Windows service.
If you are running JIRA Standalone on Linux and want to start it automatically, please refer to Starting JIRA Standalone automatically on Linux instead.
Running JIRA as a Windows service has other advantages. When started manually a console window opens, and there is a risk of someone accidentally shutting down JIRA by closing this. Also, the JIRA logs are properly managed by the Windows service (found in logs\stdout*.log
in your JIRA Home Directory, and rotated daily).
There are two ways to install JIRA as a service: via the installer, and manually.
On this page:
The easiest way to get JIRA installed as a Windows service is by clicking the 'Install JIRA as Service' check box when running the Windows installer:
You will need full Administrator rights on your Windows operating system for this installation process to complete successfully.
If you didn't use the Windows installer, or for some other reason have JIRA Standalone and now want it to run as a service, follow these instructions. They apply only to JIRA running in the Apache Tomcat application server (e.g. the JIRA "Standalone" distribution).
If you are running a 64-bit version of Windows, please note that Apache Tomcat cannot run as a Windows service if you are using a 64-bit JDK/JRE (see JRA-12965). Please ensure that you are using a 32-bit JDK/JRE.
If you used the Windows Installer, a 32-bit JDK will already have been installed for you.
On any Windows operating system with User Account Control (UAC) such as Windows Vista or Windows 7, you must either disable UAC or run 'cmd.exe' as an administrator (e.g. by right-clicking on 'cmd.exe' and selecting "Run as administrator") in order to execute the script below.
If UAC is enabled, simply logging in to Windows with an Administrator account will not be sufficient.
echo %JAVA_HOME%
.service.bat install JIRA
tomcat6 //US//JIRA --Startup auto
To see what parameters the JIRA service is starting with, Go to Start -> Run, and run "regedt32.exe".
For Windows 32 bit edition navigate to HKEY_LOCAL_MACHINE -> SOFTWARE -> Apache Software Foundation -> Procrun 2.0 -> JIRA<time stamp>
For Windows 64 bit edition navigate to HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> Apache Software Foundation -> Procrun 2.0 -> JIRA<time stamp>
tomcat6 //US//service_name --JvmMx 512
tomcat6 //US//service_name ++JvmOptions="-Djira.jelly.on=true"
tomcat6 //US//service_name ++JvmOptions="-XX:MaxPermSize=128m"
tomcat6 //US//service_name ++JvmOptions="-Xloggc:path\to\logs\atlassian-gc.log"
tomcat6 //US//service_name ++JvmOptions="-Xloggc:c:\jira\logs\atlassian-gc.log"
See the Tomcat documentation for further service options.
If JIRA was installed through the Windows installer, go to the 'Control Panel' in Windows, click 'Add or Remove Programs' and remove JIRA. This will remove the service too.
If you installed the service manually (see above) it can be uninstalled with:
service.bat remove JIRA
Alternatively, if the above does not work, use tomcat6 //DS//JIRA
.
If you are using mapped network drives for JIRA's backup directory, attachments directory, index directory or the %CATALINA_HOME%\* directory, you need to ensure that JIRA can write to these drives. That is, these directories all need to be writeable by the user which the JIRA service is running as. This may mean that you need to change the Windows user that the JIRA server uses.
Also note that you must also specify these network drives by UNC and not letter mappings, e.g. \\backupserver\jira not z:\jira
To change the Windows user that the JIRA service uses, navigate to the service in Windows, i.e. 'Control Panel' -> 'Administrative Tools' -> 'Services'. Locate the 'Atlassian JIRA' service, right-click and view the 'Preferences'.
Go to the 'Log On' tab and change the user as desired.
If you have services that depend on each other, it is important that they are started in the correct order. Common examples include:
To set up start up dependency rules, open a command prompt and enter the following command:
C:\Documents and Settings\Developer>sc config [JIRA service] depend=[database service]
Please note the space character after 'depend='
.
If you wish, you can also set up dependency rules by editing the system registry. Please see http://support.microsoft.com/kb/193888 for details on how to do this.
If you do not know the exact name of your JIRA service or your database service, you can find out what they are by following the steps below:
%JAVA_HOME%/bin
. There are two options to resolve this problem:
/temp
and /work
directories in your install directory so that this user has read and write permissions.