Duplicate :
|
web server 7.0 U2 is using jdk 5.0u12. with this version of JDK, when we run our tinderbox (continuous build system), jvm is continuously hanging. here is the stack trace from mdb mdb core > $G C++ symbol demangling enabled > $C f9159b58 libjvm.so`void PSScavengeRootsClosure::do_oop+0xaa(f9159da4, f34ad9b0) f9159b74 libjvm.so`void InterpreterFrameClosure::offset_do+0x6f(f9159bf8, 0) f9159ba4 libjvm.so`void InterpreterOopMap::iterate_oop+0x70(f9159bd0, f9159bf8) f9159c28 libjvm.so`void frame::oops_interpreted_do+0x1f0(f9159c70, f9159da4, f9159c7c, 1) f9159c48 libjvm.so`void frame::oops_do_internal+0x8a(f9159c70, f9159da4, f9159c7c, 1) f9159d88 libjvm.so`void JavaThread::oops_do+0xf1(a788c48, f9159da4) f9159db0 libjvm.so`void ThreadRootsTask::do_it+0x4a(87c45f8, 82783c8, 0) f9159e3c libjvm.so`void GCTaskThread::run+0x1ef(82cbb48) f9159fd8 libjvm.so`void*_start+0xd2(82cbb48) f9159fec libc.so.1`_thr_setup+0x4e(fc8b1400) f9159ff8 libc.so.1`_lwp_start(fc8b1400, 0, 0, f9159ff8, fd17fc10, fc8b1400) > $r %cs = 0x003b %eax = 0x087477e8 %ds = 0x0043 %ebx = 0xfc3fa000 %ss = 0x0043 %ecx = 0xf3600000 %es = 0x0043 %edx = 0xe1200000 %fs = 0x0000 %esi = 0xf91ed56c %gs = 0x01c3 %edi = 0x00000000 %eip = 0xfbeb9a9a libjvm.so`void PSScavengeRootsClosure::do_oop+0xaa %ebp = 0xf9159b58 %kesp = 0x00000000 %eflags = 0x00000286 id=0 vip=0 vif=0 ac=0 vm=0 rf=0 nt=0 iopl=0x0 status=<of,df,IF,tf,SF,zf,af,PF,cf> %esp = 0xf9159b50 %trapno = 0xe %err = 0x6 Per direction from Poonma, I am providing the location of the core for a case with a simlar issue. core file location: /net/cores.central/cores/65590895/uat1 hotspot fatal error log is also attached. Filed a separate CR 6590196 JVM crash with SEGV in PSScavengeRootsClosure::do_oop to track the "new" case. Please refer to the new CR for radiance case 65590895, raised by sriram.natarajan and steve.mui.