Universal Messaging 10.3 | Installation Guide | Post-Installation Procedures | The Dump file for Out-of-Memory Errors (OOME)
The Dump file for Out-of-Memory Errors (OOME)
Universal Messaging automatically generates a heap dump file when an OutOfMemoryError (OOME) occurs in the JVM. The default directory where heap dump files are generated is:
where <InstallDir> is the disk location where the product is installed and <InstanceName> is the name of the Universal Messaging server instance that is running in the JVM.
In addition, when Universal Messaging is using the Azul Zulu JVM (which is included in the Universal Messaging distribution kit on the Windows, Linux and Solaris platforms), or an Oracle HotSpot JVM, the generated heap dump file will be compressed in a zip archive and older heap dump files will be deleted, preserving only the 10 most recent heap dumps files.
For JVMs of other suppliers, heap dumps are stored as is (no compression and no cleanup of older dump files).
Changing the dump file location
If you wish to configure a different heap dump directory than the default, proceed as follows:
1. Using a text editor, open the file Server_Common.conf that is located in <InstallDir>/UniversalMessaging/server/<InstanceName>/bin.
2. Adapt the HEAP_DUMP_DIR environment variable.
You can specify an absolute path or a relative path. If you specify a relative path, the value must be relative to the location of the Server_Common.conf file.
When using the Oracle HotSpot JVM, the configured location must already exist, since it is not created automatically.
The changes take effect at the next restart of the server instance.