JVM crash in Linux

[ragav123]

Hi,
The following error occurred when our application ran in a Linux Server. The RAM capacity is 64GB. The application used only 15GB at the time of crash. So, there should not be a memory issue. The jdk version is jdk1.6.0_03. Can anyone of suggest what would be reason for this error and what can be done to overcome this.
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000002a95af6a4e, pid=27143, tid=1177815392
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-b05 mixed mode)
# Problematic frame:
# V [libjvm.so+0x474a4e]
#
# An error report file with more information is saved as hs_err_pid27143.log
#
# If you would like to submit a bug report, please visit:
# HotSpot Virtual Machine Error Reporting Page
#

Some more details
o Operating system and its specification
Linux version 2.6.9-89.0.9.ELlargesmp (mockbuild@x86-002.build.bos.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)) #1 SMP Wed Aug 19 08:12:11 EDT 2009
o Processor details
Intel(R) Xeon(R) CPU E7330 @ 2.40GHz
o Memory
64GB RAM

[masijade]

What is in the file "hs_err_pid27143.log"?

[ragav123]

We dont have the file with us. But which would have caused this sudden JVM crash? In most of the forums, they say it is JVM issue, In some, they say Processor Issue.

[masijade]

That log will give you more information. Without that you're only guessing.

[Tolls]

All we can say is there was a segmentation fault (null pointer by the looks of it) in the JVM, but whether that was you, the JVM, or the system we can't say.

[ragav123]

I have attached "hs_err_pid27143.txt" log you have asked. I went through the log. But it has lot of memory details which I cant understand. Hope anyone of you can understand and confirm where the issue is.

[masijade]

All I can really do is to point you here, and, of course, the link in the error itself.

The document above is 1.5, but somewhere in the same area should be an equivalent for 1.6, and that document itself is still not bad for 1.6

[ragav123]

:). Okay.. I will go through the doc. Thanks for your immediate and prompt response.

[toadaly]

Usually, JVM crashes are caused by 1 of two issues:

- The installed jar/class files were changed while the jvm was running. This happens a lot in development environments where new installs are getting pushed out, or you recompile while you're running

- You are using JNI and your code causes a seg fault.

[Tolls]

And this is a seg fault, since that's what a SIGSEGV means doesn't it?
And I took a guess at 0xb implying a null pointer.

[toadaly]

Yah, segfault = segmentation violation - an attempt to access memory outside the process space, which is the same as SIGSEGV.