Jira Running on Windows can be Randomly Terminated due to Inadequate Resources Allocated to the Virtual Machine
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs 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
Summary
When Running Jira on a Windows Virtual Machine, if the VM is not allocating enough RAM to the Jira Application then Windows can terminate Jira without any notice. In these conditions, when you try to restart Jira, tomcat's http connector will never hit a "starting" status when you try to restart.
Environment
Jira
Windows OS
Single Node Jira Environment
Jira is not the only application running on the shared virtual machine. In this case, Assets Discovery was also running on the same Virtual Machine
Diagnosis
Although you will not find anything in Jira's logs, you could find the following nested in the Windows Event Viewer, or Virtual Machine Logging
Windows Event Viewer
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
System Log
Event ID: 2004
Source: Resource-Exhaustion-Detector
Level: Warning
Message: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: tomcat9.exe.x64.exe (5180) consumed 27647913984 bytes, Discovery.exe (4064) consumed 9926320128 bytes, and MsMpEng.exe (3600) consumed 247394304 bytes.
System Log
Event ID: 26
Source: Application Popup
Level: Information
Message: Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.
System Log
Event ID: 7034
Source: Service Control Manager
Level: Error
Message: The Atlassian Jira service terminated unexpectedly. It has done this 1 time(s).
Cause
There is not enough RAM allocated to the Windows OS running Jira even though the Windows Performance Monitor might indicate that nothing exceeds a normal threshold.
Solution
To resolve this issue, increase the resources allocated to the Windows Virtual Machine so that it can successfully run Jira. Alternatively, reduce the number of other applications running on the same virtual machine in order to free resources that would normally be used by Jira.
Was this helpful?