If MailArchiva runs out of memory, unpredictable results can occur. For example, the server may stop archiving emails or the JVM under which MailArchiva runs will exit entirely.
 

When the server behaving erratically, check the debug.log file for OutOfMemory errors. Normally, if there is an OutOfMemory error, the reason is outputted in the debug.log file.

There are three possible causes for the error:
 

1. Not enough heap space is allocated (java.lang.OutOfMemoryError: Heap space)
   
   There may be a large volume of email archive traffic being processed by the server, causing the email archiving server to allocate numerous objects on the heap.

Note: In high volume environments, your server will require more memory than usual. 

3. Not enough virtual memory (java.lang.OutOfMemoryError: MappedByteBuffer).
   
   This normally indicates that too much Java heap space has been allocated MailArchiva process. MailArchiva is unable to allocate enough virtual memory (memory allocated outside of the virtual environment). 

Resolutions 

1. Heap Space: Increase The Amount of Memory Allocated To MailArchiva

Refer to Memory Settings for instructions on how to allocate more memory to MailArchiva.

2. Upgrade Your Email Archive Software To Latest Version

Visit http://www.mailarchiva.com/downloads to download the latest version
 

3. Virtual Memory: Decrease Heap Space

This memory is allocated outside of the JVM environment. Decrease the amount of heap space to between 1/3 and 1/2 of total physical RAM on the machine. 

Linux Process Dies (OOMKiller)

The Linux OS may kill the MailArchiva process unexpectedly and unnecessarily, even though MailArchiva memory management is behaving responsibly. When this scenario occurs, the following log entry is found in the Linux kernel logs (run dmesg on the Linux terminal):

Most likely the server is running out of virtual memory. It is not necessary to increase heap size. Either make available more physical memory to the server or enable the swap.