JIRA Documentation

JIRA 6.3 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

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

After giving JIRA a large amount of heap memory, errors like this appear in the logs:

In some cases the JVM will terminate with a HotSpot error. The Error message usually refers to being "out of swap space" even if the system has sufficient swap:

Cause

This is caused by a bug in 32-bit Sun JVMs. You can read about Sun's bug in their issue tracker.

Workaround

There is a workaround implemented by Lucene which has been incorporated into JIRA 4.1. This works for most memory sizes, but large heap sizes will still encounter this problem.

Upgrade to JIRA 4.1+ to implement the Lucene workaround.

Resolution

If the workaround has not helped or you cannot upgrade, give JIRA less heap by changing your JVM parameters or switch to a 64-bit JVM.

Related Content

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