JIRA Documentation

JIRA 6.4.x
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation


Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata


Symptoms include:

  1. JIRA crashes
  2. The Mail Queue is not flushed, and JIRA is no longer sending out email notifications.
  3. The Activity stream or search is not updated with recent content

The following appears in the atlassian-jira.log:


The JVM running JIRA has hit an OutOfMemory Error (OOME). This is thrown when the Java Virtual Machine cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector.

After an OutOfMemory error, the Java Virtual Machine (JVM) will likely be in an unstable state and hence it is essential to restart JIRA immediately.


If you receive an OutOfMemory Error, follow these instructions to increase the memory available to JIRA and also to enable logging for garbage collection:

  1. Are you in the right place? This page refers to Heap Space Memory issues, as indicated by the snippet in the Symptoms description. There are a set of other memory related problems such as the following.

    (info) Please use the appropriate KB based on the error in the logs.
  2. Stop JIRA.
  3. Increase the maximum memory available to the JVM as per our Increasing JIRA Memory docs. We recommend small increases of 256m at a time or 512m for larger instances.
  4. Enable Garbage Collection (GC) logging as per Using Garbage Collection Logs to Analyze JIRA Performance.
  5. Start JIRA so that the changes to memory and GC logging are in effect.

Our Troubleshooting Performance Problems KB contains further information on troubleshooting these problems. As a follow-up, proceed with the steps below for a root cause analysis:

Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?