###@###.### 2004-03-30

J2SE Version (please include all output from java -version flag):
  java version "1.5.0-beta2"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b42)
  Java HotSpot(TM) 64-Bit Server VM (build 1.5.0-beta2-b42, mixed mode)

Does this problem occur on J2SE 1.3.x or 1.4.x? Yes / No (pick one)
  No (There is no 1.4.x for AMD64 - public 1.5.0 beta even don't work)

Operating System Configuration Information (be specific):
  Fedora Core Linux 1 for x86-64
  glibc 2.3.2
  Linux kernel 2.4.25 - Custom
  Linux opteron 2.4.25 #6 SMP Tue Mar 23 17:26:48 CET 2004 x86_64 x86_64
  x86_64 GNU/Linux

Hardware Configuration Information (be specific):
  Opteron 2x 240
  Tyan Tiger K8W
  4 GB 266Mhz ECC DDR
  72GB hard disk drive on LSI MegaRaid

Bug Description:
  When customer's java server aplication is running under heavier load, jvm
  processes hang and utilize 100% of one cpu, check attached full stack dump
  with kill -QUIT java (ftd-b42-opteron-v2, ftd-b42-opteron)

  jvm sometimes also crashes. check attached hs_err_pid7666.log file.

Steps to Reproduce (be specific):

  run a server application with the following command line options:

  -Xrunhprof:cpu=samples,depth=50,thread=y
  -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
  -Djava.awt.headless=true -Xms512M -Xmx1024M


  

###@###.### 2004-06-01

More failure report from the customer:

When their application is running under heavy load with
"-client -XX:+UseSerialGC" flags, it worked before at Tiger
build50 but JVM hangs with build51, check the Full Thread
Dump file(Ftd-1.txt)

Here is the summary report about JVM hang problem with different flags
and results:

JVM version Index on Disk Index in RAM
=======================================================================
jdk1.5.0_b50 N Y
jdk1.5.0_b50 -client N Y
jdk1.5.0_b50 -client -XX:+UseSerialGC N Y
jdk1.5.0_b50 -server N N
jdk1.5.0_b51 N Y
jdk1.5.0_b51 -client N Y
jdk1.5.0_b51 -client -XX:+UseSerialGC N N <---- works with b50
jdk1.5.0_b51 -server N N

Trident3 Index server can run into 2 modes - with index in RAM
or with index on hard disk. Y means it is running OK, N means not running.

Index in RAM version has bigger heap space (about 3-4gb) and
disk version is running with 1 gb of heap (-MXm).