NextGen Knowledge Center

Out of Memory Errors

By default, the max Java heap size for the Mirth® Connect server is set to 256 MB. For large production instances you typically want to increase this value. You can do this from the Server Manager:

Or, you can edit the appropriate *.vmoptions file in your installation directory.

Out of memory errors can also happen on the client-side, usually when attempting to view very large messages through the message browser:

Animage of an out of memory error

If this is the case, first you may want to consider using attachment handlers on your channel. To change the max heap size for the client-side Administrator, open the 8080 launch page in a browser:

Image of the launch page

Select the cog icon next to the Launch button, and change the max heap size. Then select the launch button. The JNLP file you download will have the "max-heap-size" attribute set to the value you chose.

The default value for the client-side max heap size is 512 MB. To change this default, edit the administrator.maxheapsize setting in the mirth.properties file. To change the options that show up in the drop-down on the 8080 launch page, change the administrator.maxheapsizeoptions setting.