Filed By       : J2SE-SQA [j2se-tck- xxxxx@xxxxx ]
JDK            : JDK1.5.0-b26
Testbase       : Regression-test
Platform[s]    : Solaris 8 (sparc) (CDE)
switch/Mode    : -client
Falling test[s]:
         javax/sound/midi/Sequencer/MidiCrash.java

Regression test javax/sound/midi/Sequencer/MidiCrash.java hangs with JDK1.5.0-b26 on our Solaris 8/Sparc
computer with sound. The computer is a bit slow.

The test passes on this machine with several previous Tiger builds (tested with b19-b25).

The test passed on other platforms we used for testing of b26: (RH2.1AS, WinXP, Sol9x86).

The test fails on JDK1.4.2 with VM abort (probably the issue described in 4795377).

I inserted some tracing into MidiCrash.java and found that the test hangs in
Sequencer.setSequence called from MMAMidiBridge.setSequence(Sequence s).



Test source location:
=====================
/java/re/jdk/1.5.0/promoted/all/b26/ws/j2se/test/javax/sound/midi/Sequencer/MidiCrash.java

jtr file location:
==================
/net/jtgb4u4c.sfbay/export/sail15/results.2/tiger/b26/regtest/sparc/sol8_sparc_cde_linux-1/workDir/test/javax/sound/midi/Sequencer/MidiCrash.jtr

How to reproduce:
=================
Run the following script (you may need to change its variables)

--- script start ---
#!/bin/sh
RESULT_DIR=`pwd`
WORK_DIR=$RESULT_DIR/workDir/test
REPORT_DIR=$RESULT_DIR/reportDir

#Paths in Java Software:
JT_HOME="/java/re/jct-tools/3.1.2/archive/fcs/binaries"
JEMMY_JAR="/net/jdk/export/jpse04/Jemmy/jemmy.jar"
JAVA_HOME="/java/re/jdk/1.5.0/promoted/all/b26/binaries/solaris-sparc"
TEST_BASE_PATH="/java/re/jdk/1.5.0/promoted/all/b26/ws/j2se/test"

#Alternative paths outside Java Software:
#JT_HOME="/net/koori.sfbay/onestop/jct-tools/3.1.2/archive/fcs/binaries"
#JEMMY_JAR="/net/jdk/export/jpse04/Jemmy/jemmy.jar"
#JAVA_HOME="/net/koori.sfbay/onestop/jdk/1.5.0/promoted/all/b26/binaries/solaris-sparc"
#TEST_BASE_PATH="/net/koori.sfbay/onestop/jdk/1.5.0/promoted/all/b26/ws/j2se/test"

#Alternative paths for the NSK site:
#JT_HOME="/net/linux-15/export/home/java/jct"
#JEMMY_JAR="$JT_HOME/jemmy/jemmy.jar"
#JAVA_HOME="/net/linux-15/export/home/java/jdk1.5.0/sparc"
#TEST_BASE_PATH="/net/linux-15/export/home/java/regtest.tiger/test"


TESTVMOPTS="-client"
CLASSPATH="$JT_HOME/classes:$JT_HOME/lib/javatest.jar:$JT_HOME/lib/jtreg.jar"

TEST="javax/sound/midi/Sequencer/MidiCrash.java"

mkdir -p $WORK_DIR/scratch 2>&1
mkdir -p $WORK_DIR/jtData 2>&1
mkdir -p $REPORT_DIR 2>&1

#rm $WORK_DIR/jtData/ResultCache.jtw 2>&1

cd $WORK_DIR/scratch

$JAVA_HOME/bin/java -server -cp $CLASSPATH -DenvVars=TESTJAVAHOME=$JAVA_HOME,TESTVMOPTS=$TESTVMOPTS,DISPLAY=:0,HOME=$HOME/.regtest,PATH=/bin:/usr/bin,CPAPPEND=$JEMMY_JAR,TZ=,LC_ALL=en_US,LC_CTYPE=en_US,LANG=en_US,LPDEST= -DDISPLAY=:0 -DlocalHost="linux-1" -Dprogram=jtreg com.sun.javatest.regtest.Main -a -v default -batch -params -w "$WORK_DIR" -r "$REPORT_DIR" -t "$TEST_BASE_PATH" "$TEST_BASE_PATH/$TEST"

--- script end ---


Test output (jtr part):
=======================
----------System.out:(0/0)----------
----------System.err:(0/0)----------
result: Passed. Compilation successful

#section:main
----------messages:(3/120)----------
command: main MidiCrash
reason: Assumed action based on file name: run main MidiCrash
elapsed time (seconds): 2400.032
----------System.out:(2/28)----------
Iteration 1/5
Iteration 2/5
----------System.err:(0/0)----------
result: Failed. Execution failed: Program `/net/linux-15/export/home/java/jdk1.5.0/sparc/bin/java' interrupted! (timed out?)


test result: Failed. Execution failed: Program `/net/linux-15/export/home/java/jdk1.5.0/sparc/bin/java' interrupted! (timed out?)


Specific machine info:
======================
Hostname: linux-1
OS: Solaris 8 (sparc) (CDE)



======================================================================

N/A

Probably due to the Sequencer deadlock described in 4949191. Only occurs on Ultra-1 or other slow machines.
 xxxxx@xxxxx  2003-11-13

The fix for 4949191 also fixed this regression test. I was able to reproduce this hang both on a SunBlade 100 (rarely), and always on an Ultra 1. With the fix, I ran successfully 10000 iterations of the crash test on both machines.
 xxxxx@xxxxx  2003-11-14