With hopper b06, on jtgb4u2d ( Sparc solaris 8), tomcat hang after a few iterations.
Processes are still alive. there are gcore files under /bt/Tomcatrun.4427.-d64
on jtgb4u2d.
The failure did not happen in hopper b05.
How to reproduce the bug:
1. start tomcat server
cp -r /net/jtgb4u4c/export/sail8/1.3bigapps/ws/master/dist/tomcat /bt/tomcat
cd /bt/tomcat/bin
export JAVA_ARGS="-d64"
./catalina.sh
2. start tomcat client in a loop
export CLASSPATH=/net/jtgb4u4c.sfbay/export/sail8/1.3bigapps/ws/master/dist/atg/sunperf/urlhammer.jar
export SERVER=`uname -n`
${JAVA_HOME}/bin/java ${CLIENT_JAVA_ARGS} atg.core.net.URLHammer http://${SERVER}:3030/index.html 100 200
Or to run tomcat using bigapps script
1. cd /bt
2. export JAVA_HOME=<install dir>
3. /bs/runtomcat.ksh -d64
Log files will be under /bt/Tomcat*/run*out
This looks like another GC failure probably related to the cloudscape p1 bug
and this bugid 4629175. The server process gets a Sig 11.
[8] FastScanClosure::do_oop(0xffffffff387012e0, 0xffffffff06a006b8, 0x1, 0x12,
0x5440000, 0xc2b0), at 0xffffffff7d45bb40
[9] OopMapSet::all_do(0xfc00, 0xffffffff39d1c6d0, 0xffffffff38700998, 0xffffff
ff387012e0, 0xffffffff7d30337c, 0xffffffff7d7eb998), at 0xffffffff7d232dfc
[10] OopMapSet::oops_do(0xffffffff38700978, 0xffffffff39d1c6d0, 0xffffffff3870
0998, 0xffffffff387012e0, 0xffffffff7d205034, 0xffffffff39e0ede0), at 0xffffffff
7d232ccc
[11] frame::oops_code_blob_do(0xffffffff38700978, 0xffffffff387012e0, 0xffffff
ff38700998, 0x387012e0, 0xf40, 0x0), at 0xffffffff7d232c18
[12] JavaThread::oops_do(0x1008c8710, 0xffffffff387012e0, 0xffffffff14840000,
0xc7a8, 0xffffffff7d3bde18, 0x0), at 0xffffffff7d24f510
[13] Threads::oops_do(0xffffffff387012e0, 0xffffffff387012e0, 0xffffffff7d261e
9c, 0x477940, 0xffffffff7d2c1424, 0x9c00), at 0xffffffff7d2b9f5c
[14] GenCollectedHeap::process_strong_roots(0x100187500, 0x0, 0x1, 0x0, 0x1, 0
xffffffff38701298), at 0xffffffff7d2b8c94
[15] DefNewGeneration::collect(0x100187650, 0x0, 0x0, 0x5, 0x0, 0x0), at 0xfff
fffff7d2ca8a8
###@###.### 2002-03-20
Processes are still alive. there are gcore files under /bt/Tomcatrun.4427.-d64
on jtgb4u2d.
The failure did not happen in hopper b05.
How to reproduce the bug:
1. start tomcat server
cp -r /net/jtgb4u4c/export/sail8/1.3bigapps/ws/master/dist/tomcat /bt/tomcat
cd /bt/tomcat/bin
export JAVA_ARGS="-d64"
./catalina.sh
2. start tomcat client in a loop
export CLASSPATH=/net/jtgb4u4c.sfbay/export/sail8/1.3bigapps/ws/master/dist/atg/sunperf/urlhammer.jar
export SERVER=`uname -n`
${JAVA_HOME}/bin/java ${CLIENT_JAVA_ARGS} atg.core.net.URLHammer http://${SERVER}:3030/index.html 100 200
Or to run tomcat using bigapps script
1. cd /bt
2. export JAVA_HOME=<install dir>
3. /bs/runtomcat.ksh -d64
Log files will be under /bt/Tomcat*/run*out
This looks like another GC failure probably related to the cloudscape p1 bug
and this bugid 4629175. The server process gets a Sig 11.
[8] FastScanClosure::do_oop(0xffffffff387012e0, 0xffffffff06a006b8, 0x1, 0x12,
0x5440000, 0xc2b0), at 0xffffffff7d45bb40
[9] OopMapSet::all_do(0xfc00, 0xffffffff39d1c6d0, 0xffffffff38700998, 0xffffff
ff387012e0, 0xffffffff7d30337c, 0xffffffff7d7eb998), at 0xffffffff7d232dfc
[10] OopMapSet::oops_do(0xffffffff38700978, 0xffffffff39d1c6d0, 0xffffffff3870
0998, 0xffffffff387012e0, 0xffffffff7d205034, 0xffffffff39e0ede0), at 0xffffffff
7d232ccc
[11] frame::oops_code_blob_do(0xffffffff38700978, 0xffffffff387012e0, 0xffffff
ff38700998, 0x387012e0, 0xf40, 0x0), at 0xffffffff7d232c18
[12] JavaThread::oops_do(0x1008c8710, 0xffffffff387012e0, 0xffffffff14840000,
0xc7a8, 0xffffffff7d3bde18, 0x0), at 0xffffffff7d24f510
[13] Threads::oops_do(0xffffffff387012e0, 0xffffffff387012e0, 0xffffffff7d261e
9c, 0x477940, 0xffffffff7d2c1424, 0x9c00), at 0xffffffff7d2b9f5c
[14] GenCollectedHeap::process_strong_roots(0x100187500, 0x0, 0x1, 0x0, 0x1, 0
xffffffff38701298), at 0xffffffff7d2b8c94
[15] DefNewGeneration::collect(0x100187650, 0x0, 0x0, 0x5, 0x0, 0x0), at 0xfff
fffff7d2ca8a8
###@###.### 2002-03-20
- duplicates
-
JDK-4651825 64 bit VM crash: assert(obj->is_oop(), "sanity check")
- Closed
- relates to
-
JDK-4629175 JVM crash.... Error : 11
- Resolved