Configuring JIRA Service to Run on a Different JVM
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
To configure JIRA service to run on different JVM rather then the default one which is bundled with JIRA installation, the JVM parameter of the JIRA service has to be modified. To modify JIRA's service parameters, follow these steps:
- In the services list, find JIRA's service.
Right click, go to properties and find the value of the "Path To Executable" parameter. It looks something like
"C:\Program Files\Atlassian\JIRA\bin\tomcat7.exe" //RS//JIRA070313174758Replace tomcat7.exe with tomcat7w, and RS with ES, and it will provide you with a command like the following:
"C:\Program Files\Atlassian\JIRA\bin\tomcat7w.exe" //ES//JIRA070313174758- Run that command from a command console.
- In the Java tab of the configuration window that opens, change the 'Java Virtual Machine' setting to use the new location of the jvm.dll.
- Restart the service 'Atlassian JIRA'.