• Post Reply Bookmark Topic Watch Topic
  • New Topic

Java core dump  RSS feed

 
Micki Tomas
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My JVM seems to be getting killed whenever I run a Cactus testcase (junit testcases run fine), regardless of what I do inside the testcase.

JVMDG217: Dump Handler is Processing Signal 11 - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to C:\logs\javacore.20060406.104947.3432.txt
JVMDG215: Dump Handler has Processed Exception Signal 11.

Any idea what this could be??? I have seen dumps from C/C++ apps before, but not Java.

The core file says "Fault module: C:\WINDOWS\System32\ntdll.dll"
 
Tony Morris
Ranch Hand
Posts: 1608
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A JVM that core dumps is defective - assuming no user-supplied native code is used and no dependencies of the JVM are defective. Post the core dump and narrow down exactly what produces the segmentation fault.
 
Ulas Ergin
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Signal 11 is SIGSEGV (Segmentation Violation) and this error is coming from the JVM level (namely from a C application)

what it calls 'javacore' is in fact a dump of stack traces at the moment the error has occured for you to give a hint (in this case I don't think it will help much since it will be on Java level not C)
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!