Confluence Docs 3.0 : Fix Out of Memory errors by Increasing Available Memory This page last changed on Oct 05, 2009 by jlargman.
| JDK 1.4 does not provide information why the `OutOfMemory` error occurred. Since Confluence version 2.8, this JDK is not supported any longer. JDK 1.5 or 1.6 are the recommended JDK to be used and they do provide a description of the OOM error. JDK 1.6 also has around a 20% performance improvement over 1.5
Since the default memory setting usually is around 64 or 128MB (256MB in Confluence 2.2 and later), you might have to adjust the settings to run a bigger Confluence instance with sufficient memory. On this page: Diagnosis and Common Causes Determining the various causes of memory errors java.lang.OutOfMemoryError: PermGen space java.lang.OutOfMemoryError OutOfMemoryError: unable to create new native thread OutOfMemoryError: GC overhead limit exceeded OutOfMemoryError: Requested array size exceeds VM limit Setting the Memory Settings RELATED TOPICS # Diagnosis and Common Causes There are several reasons that out of memory exceptions can be thrown. Either the virtual machine Confluence is using has hit its allocated memory limit, the system on which Confluence is running has run out of physical and virtual memory, or Confluence is consuming too much memory. In the first case, you should modify the maximum heap size of the virtual machine, per the instructions in this document; in the second or third cases, the solution is to identify the culprit of the memory leak. For help determining which memory settings to choose, consult Managing Application Server Memory Settings. If you have not yet set your memory settings and your usage has increased, it's likely that you must set your memory, described below. If your usage patterns have not changed but you've added a plugin or done an upgrade, it's likely that there is a memory leak in a plugin. If you're using the in-memory database (HSQLDB), migrate to an external database. The in-memory database can use a lot of memory. If you are using XML backups, disable them and move to the Alternative Backup Strategy. The XML backup process can be a memory hog. To troubleshoot potential memory leaks, enter Plugin Support Mode. Take thread dumps during normal operations and during an outage, and submit this information in a support ticket. # Determining the various causes of memory errors There are different kinds of memory limits inside the Java Virtual Machine. Each limit can be configured independently. But you must first find out which limit you have reached. #### java.lang.OutOfMemoryError: PermGen space If you get the error message: `java.lang.OutOfMemoryError: PermGen space` this means that you have exceeded Java's default 64Mb block for loading class files. This can happen if many plugins are installed. You may want to increase the PermGen memory size to suit your needs. In the following sample, the blue parameter shows how the PermGen Memory has been set to 192 megabytes. This value should be set depending on your memory requirements. 192m should be sufficient for Confluence even when many plugins are installed. JAVA_OPTS="-Xms128m -Xmx1024m -XX:MaxPermSize=192m $JAVA_OPTS -Djava.awt.headless=true " Note: The other parameters in this sample are just shown to give you some context, and are not part of this example. #### java.lang.OutOfMemoryError Heap space memory errors occur when the application has to deal with large amounts of data or users. These errors will contain only a `java.lang.OutOfMemoryError`, e.g. without the reference to PermGen space as above. You should try to increase the heap size to solve this problem. This requires configuring the Xmx and Xms parameters. In the following example, the maximum heap size is set to 1024 megabytes. This should be enough for small to medium deployments. JAVA_OPTS="-Xms128m -Xmx1024m -XX:MaxPermSize=256m $JAVA_OPTS -Djava.awt.headless=true " Note: The other parameters are only shown to give you context and are not part of this example. Deployments with high usage patterns may require additional memory. For high-usage deployments, it is recommended to set both Xms and Xmx as the same value (eg. -Xms1024m -Xmx1024m), _provided the memory is available_. On the other hand, adding too much memory can also cause problems (see below), so you should increment memory carefully, for example in increments of 128 megabytes. #### OutOfMemoryError: unable to create new native thread This error occurs when the operating system is unable to create new threads. This is due to the JVM Heap taking up the available RAM. Big heaps take away from the space that can be allocated for the stack of a new thread For 32bit Linux generally the maximum heap size of the JVM cannot be greater than 2GB. Windows systems will typically split the available physical memory 50:50 as Application and Kernel/System space, so please do not allocate an amount exceeding or approaching that split. The size of the stack per thread can also contribute to this problem. The stack size can reduce the number of threads that can be created. To fix this problem, you should reduce the size of your JVM Heap and also the size of the stack per thread. The stack size can be changed with the following (example) parameter: "-Xss512k" Please refer to this guide as a reference for JVM tuning. #### OutOfMemoryError: GC overhead limit exceeded This error indicates that the JVM took too long to free up memory during its GC process. This error can be thrown from the Serial, Parallel or Concurrent collectors. It often means that the Xmx value is too high - you might consider lowering it. See Garbage Collector Performance Issues for more details. For more severe and persistent performance issues relating to GC, it is recommended to change to a parallel collector, and to ensure that Confluence has access to the memory demanded by its users. The parallel collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown. This feature is designed to prevent applications from running for an extended period of time while making little or no progress because the heap is too small. If necessary, this feature can be disabled by adding the option -XX:-UseGCOverheadLimit to the command line. This kind of OutOfMemoryError can be caused if user requests drown the available resources in the JVM. When this occurs, performance will degrade aggressively. This will eventually require a restart or the application may recover. #### OutOfMemoryError: Requested array size exceeds VM limit This is a rare error and indicates that Confluence attempted to allocate an array that is larger than the Java heap size. More details regarding this error can be found here. This is due to a known limitation of the JVM as documented here. We have a bug lodged against this, to better handle this exception in Confluence. # Setting the Memory Settings How to set the heap or permanent generation memory depends on your distribution, platform, and how you start Confluence. Refer to Configuring System Properties.
| If you're starting Confluence from a Windows Service, make sure you add the properties through the registry settings.
| To verify if your settings have been picked up, check Displaying System Properties.
| Other factors such as system load and allocating too much memory to your JVM Heap can also cause OutOfMemory Errors. For more information, you can refer to the JIRA documentation on Causes of OutOfMemoryErrors.
##### RELATED TOPICS Managing Application Server Memory Settings Installing the Confluence EAR-WAR Edition FAQ Home Tomcat JVM options and Modify the Default JVM Settings Websphere Tuning JVM Logging A Thread Dump Attachments: 1.JPG (image/jpeg) 2.JPG (image/jpeg) 3.JPG (image/jpeg)

Document generated by Confluence on Nov 05, 2009 23:34