If Confluence runs out of memory, what should you do?

• A. Decrease heap memory
• B. Restart Confluence without changes
• C. Disable users
• D. Increase the heap memory

Answer: (D)

When Confluence runs out of memory, the underlying issue is that the Java heap allocated to the Confluence process is exhausted. The JVM stores pages, caches, indices, and other active data in that heap, so once it’s full, performance deteriorates or you hit memory errors. The correct move is to increase the heap memory allocated to the Confluence JVM (adjust the Xmx value, and ideally Xms as well) so there’s more room for objects and for the garbage collector to operate effectively. After changing the heap size, restart Confluence and monitor memory usage to ensure the system has enough RAM and that garbage collection isn’t thrashing. Decreasing the heap, restarting without changes, or disabling users don’t address the root cause; they either worsen the available space, provide only a temporary relief, or simply reduce load without solving memory capacity issues.