Missing Core Dumps

Shutdowns on UNIX almost always cause the system to dump a core file, usually in the directory from which the process initially loaded.

See Also
Collecting Logs and Core Files
mx_err_pid.log for Windows
Java Activation Error on the ENOVIA Live Collaboration Server

If no core dump file is generated, you might need to enable core files, as described below:

Enabling Core Files
Windows

To enable minidumps (core dump equivalent) on Windows, add the following parameter to JVM options for Tomcat: 

-XX:+CreateMinidumpOnCrash
Thick client (mql)

To enable minidumps in the thick client (mql), set the following parameter in the environment (NOT in enovia.ini): MX_IRM_ENABLE=TRUE.

This will result in the following message on mql startup:

Notice: #1600100: Incident Report Management enabled

On crash, this message will be generated:

-----------------------> Watchdog suspends all threads
-----------------------> Watchdog resumes all threads

A zip file containing mdmp will be generated in the %TMP%\DSYSysIRManager\Incident directory.

Linux Use:
ulimit -c unlimited