JVM Crash原因分析及相关资料

去年生产环境突然有一天连续发生几台服务器jvm crash的情况。出现这种情况的时候jvm留下的error log基本相同

## a fatal error has been detected by the java runtime environment:##  sigsegv (0xb) at pc=0x00002b28192a24f0, pid=28485, tid=1088477504## jre version: 6.0_18-b07# java vm: java hotspot(tm) 64-bit server vm (16.0-b13 mixed mode linux-amd64 )# problematic frame:# v  [libjvm.so+0x5c04f0]## 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 (0x00002aab4803e800):  javathread "compilerthread1" daemon [_thread_in_native, id=28511, stack(0x0000000040d0d000,0x0000000040e0e000)]siginfo:si_signo=sigsegv: si_errno=0, si_code=1 (segv_maperr), si_addr=0x000000000000002c此处略去n个字...current compiletask:c2:171% !   org.mule.esb.impl.core.provider.spring.esbclientbean.invoke(ljava/lang/reflect/method;[ljava/lang/object;)ljava/lang/object; @ 56 (492 bytes)再次略去n个字...

巧合的是crash时jvm都在做同一件事情“current compiletask:
c2:171% ! org.mule.esb.impl.core.provider.spring.esbclientbean.invoke(ljava/lang/reflect/method;[ljava/lang/object;)ljava/lang/object; @ 56 (492 bytes)”
显示jit在做编译优化的时候处理.esbclientbean.invoke这个方法时出错。幸好sun（oracle）提供了相关的文档说明，得以让我们解决了这个问题。
文档地址：[url=http://www.oracle.com/technetwork/java/javase/crashes-137240.html#gbyzu]http://www.oracle.com/technetwork/java/javase/crashes-137240.html#gbyzu[/url]
<div class="quote_title">引用