• Post Reply Bookmark Topic Watch Topic
  • New Topic

A fatal error has been detected by the Java Runtime Environment: Internal Error (buildOopMap.cpp)  RSS feed

 
Lavanya Thirumalaisami
Greenhorn
Posts: 3
Java jQuery
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying to run a process in my web application, my server restarts for the first time when I run the process with the error " A fatal error has been detected by the Java Runtime Environment:". I have attached part of my Java Fatal Error Log.
Please let me know if you have any suggestions. This is happening occasionally.


#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (buildOopMap.cpp:291), pid=18810, tid=47382814927168
# Error: guarantee(0,"must find derived/base pair")
#
# JRE version: 6.0_15-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.1-b02 mixed mode linux-amd64 )
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

--------------- T H R E A D ---------------

Current thread (0x000000005aa54800): JavaThread "CompilerThread0" daemon [_thread_in_native, id=18818, stack(0x00002b182bca2000,0x00002b182bda3000)]

Stack: [0x00002b182bca2000,0x00002b182bda3000], sp=0x00002b182bd9ea50, free space=1010k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x6bd12f]
V [libjvm.so+0x2be4d6]
V [libjvm.so+0x207d72]
V [libjvm.so+0x2078fa]
V [libjvm.so+0x2081fc]
V [libjvm.so+0x59bd3c]
V [libjvm.so+0x281ccd]
V [libjvm.so+0x27e2e4]
V [libjvm.so+0x212d6e]
V [libjvm.so+0x286fa8]
V [libjvm.so+0x286946]
V [libjvm.so+0x682129]
V [libjvm.so+0x67bbf1]
V [libjvm.so+0x5971af]


Current CompileTask:
C2:2864 com.intershop.beehive.xcs.pipelet.productset.AssignProductToProductSet.execute(Lcom/intershop/beehive/core/capi/pipeline/PipelineDictionary;)I (129 bytes)
 
Mike Degteariov
Ranch Hand
Posts: 145
8
Java Mac MySQL Database Ubuntu
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Has it only started crashing recently?

This could be genuine JVM bug, of course, but this could be a bug in native library loaded by the project just as likely.

We once had a similar problem when JBoss started crashing with JVM native error. We were fortunate enough to notice that the problem appeared after a new library was added to the project. In this case, the was partially implemented using native code, and it crashed every once in a white for some reason.

So I'd suggest to check if you have any third party libraries that use native code. They could cause this.
 
Henry Wong
author
Sheriff
Posts: 23295
125
C++ Chrome Eclipse IDE Firefox Browser Java jQuery Linux VI Editor Windows
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Lavanya Thirumalaisami wrote:
Current thread (0x000000005aa54800): JavaThread "CompilerThread0" daemon [_thread_in_native, id=18818, stack(0x00002b182bca2000,0x00002b182bda3000)]


Weird. It looks like it may be related to the Just in Time compiler. Perhaps, one thing to try is to disable the JIT compiler.

Of course, it is not recommend to run without the JIT compiler. I am only making this recommendation as a test to confirm or disprove that it is relate to a JIT compiler issue.

Henry
 
Lavanya Thirumalaisami
Greenhorn
Posts: 3
Java jQuery
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Mike, thanks for the reply, The error started occurring from May we have not noticed it till now. The process was running fine till then without any issues. There were lot of changes made to the server as part of performance tuning but there were new libraries added as part of some bug fixes for the product, I will verify these libraries and test them out. This issue is happening only in production environment and is not happening any other servers,
 
Lavanya Thirumalaisami
Greenhorn
Posts: 3
Java jQuery
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Henry, Thanks for the suggestion, I will try to disable JIT and test this process and enable it back. Would update you if this helps.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!