JDK-4918466 : Bigapp Vmark test error cause the test to hang.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2_02
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: linux
  • CPU: itanium
  • Submitted: 2003-09-06
  • Updated: 2014-02-27
  • Resolved: 2007-08-03
Related Reports
Relates :  
JDK-4990024 - Bigapp Vmark and Vtest received test failure
Relates :  
JDK-6177677 - VolanoMark bigapp is failing on win2003 EE with 1.4.2_X
Description
While running Bigapp-Vmark test with jdk1.4.2_02 (64 bit) on Itanium II machine with Red Hat Enterprise Linux (Advanced Server 3.0). The test run in to this error and it hang the whole test. Enclose is the error message that I got when the test was hung.

Here is the Kernel and OS version information.
Linux urt-it-1 2.4.21-1.1931.2.399.ent #1 SMP Wed Aug 20 15:23:44 EDT 2003 ia64 ia64 ia64 GNU/Linux
[root@urt-it-1 root]# cat /etc/red*rel*
Red Hat Enterprise Linux release 2.9.5AS (Taroon)

run.vmark: Iteration # 163
run.vmark: Current date : Fri Sep  5 16:58:47 PDT 2003

VolanoMark(TM) Benchmark Version 2.1.2
Copyright (C) 1996-1999 Volano LLC.  All rights reserved.
Creating room number 1 ...
20 connections so far.
Creating room number 2 ...
40 connections so far.
Creating room number 3 ...
60 connections so far.
Creating room number 4 ...
80 connections so far.
Creating room number 5 ...
100 connections so far.
Creating room number 6 ...
120 connections so far.
Creating room number 7 ...
140 connections so far.
Creating room number 8 ...
160 connections so far.
Creating room number 9 ...
180 connections so far.
Creating room number 10 ...
200 connections so far.
Running the test ...
Unexpected Signal: 11, PC: 0x2000000000a06a50, PID: 10419
An error has just occurred.
To debug, use 'gdb /usr/j2se/bin/java 10419'; then switch to thread 16386
Otherwise, press RETURN to abort...
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_06
23-06-2004
EVALUATION Reproducible on linux-ia64. Once the SIGSEGV is thrown, the entire system (java) seems to be in a stale state. There were 381 threads (linux lpw) at that instance. ###@###.### 2003-10-23 The hang is due to -XX:+ShowMessageBoxOnError argument. Without this, the crash do happen but the test system is running continously. ###@###.### 2004-01-14 The crash report gives the following function: copy_to_survivor_space__16DefNewGenerationP7oopDescPP7oopDesc+0x20 This is a DefNewGeneration::copy_to_survivor_space(oopDesc, oopDesc*) call. And hence the failing thread is a GC thread. At the time of crash, the heap has 100% usage of eden space. Most of the threads are in the SafePoint waiting state. When using with -XX:-UseCompilerSafepoints, the problem does not reoccur. ###@###.### 2004-06-14
14-06-2004