When the JVM crashes, you usually don't see anything in the log. The server just stops, sometimes showing a message in the console. It dumps information about the JVM crash on the console, or in a file called hs_err_pidXYZ.log with XYZ being a number. It happens outside of Nuxeo's scope, and is not due to Nuxeo bugs.
We reference in this page ways to work around known JVM crashes.
JIT Compiler Crashes
Some of the crashes happen in the JIT compiler thread. This can be detected by messages in the JVM crash report like:
The class reported can be different, for each of them you should add a JAVA_OPTS parameter (i.e., in run.conf) like:
The above has been reported with Sun JVM 1.5.0_17.
Another JVM crash reported on linux 32- and 64-bits with Sun's JVM version 1.5.0_18 looks like:
This can be solved by adding to JAVA_OPTS:
AWT Crashes
On Mac OS X, some crashes happen in the AWT bridge. They mention:
Disabling AWT (not used anyway by Nuxeo) may fix the problem. Add to JAVA_OPTS: