JRockit Crashes with empty dump file.

Question

---Symptom:
JRockit creates an empty dump file and dies without fully starting
Dump file looks like this:
     [user@computer some_dir]$ cat jrockit.25058.dump
     ===== BEGIN DUMP ===============================
     [user@computer some_dir]$
---Cause:
ulimit -s 2048
This limits the stack size which apparently causes problems for JRockit.
This limit had been set to workaround a known issue in the Sun JVM.
---Workaround:
Use system default stack size or a size larger than 2048.
---Environment:
Java:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
BEA WebLogic JRockit(TM) 1.4.2_04 JVM (build ari-31788-20040616-1032-linux-ia32, Native Threads, GC strategy: parallel)
OS:
Linux DL580 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux

Answer 1

Bandas,
The crash most likely happens because you have very little memory left on your system.
In the dump you can find the following message:
"C Heap : 3 memory allocations have failed"
This indicates that three malloc have failed internally. Given additional information in the dump it looks like an allocation did fail during garbage collection internally within the JVM that caused this crash. We have been working at improving the error message on these kinds of complete out of memory situations.
The best thing you can do is to reduce the java-heap size which will make more native memory available.
Another thing you can try if you haven't is to boot up windows in /3GB mode which will give JRockit access to the an additional 1GB of memory. (Your machine seem to have 3GB+ memory so booting Windows with the /3GB switch will allow JRockit to take advantage of that memory)
I hope this helps