We're updating the issue view to help you get more done. 

Intermittent Object.notify() failure in Xalan with Base compiler

Description

A clean checkout of trunk using "production_Base" failed to complete Xalan 14 times out of 100 runs on a 8 core Nehalem Linux box with HyperThreading enabled (16 logical processors). The 14 failures all gave the same error which is shown below.

This error also exhibited itself on 2/100 production_Base runs on a 2*2 core PowerPC box. On both dual core and single core x86 systems this error did not show up in 100 production_Base runs.

===== DaCapo xalan starting =====
java.lang.IllegalMonitorStateException: notifyingdacapo.xalan.XalanHarness$WorkQueue@2576d16e
java.lang.IllegalMonitorStateException: notifyingdacapo.xalan.XalanHarness$WorkQueue@2576d16e
at org.jikesrvm.scheduler.RVMThread.raiseIllegalMonitorStateException(RVMThread.java:3034)
at org.jikesrvm.scheduler.RVMThread.notify(RVMThread.java:3052)
at java.lang.Object.notify(Object.java:52)
at dacapo.xalan.XalanHarness$WorkQueue.push(XalanHarness.java:45)
at dacapo.xalan.XalanHarness.iterate(XalanHarness.java:198)
at dacapo.Benchmark.run(Benchmark.java:126)
at dacapo.TestHarness.runBenchmark(TestHarness.java:302)
at dacapo.TestHarness.main(TestHarness.java:242)
at Harness.main(Harness.java:5)

Environment

ia32-linux and ppc32-linux

Status

Assignee

Unassigned

Reporter

Laurence Hellyer

Labels

None

External issue ID

None

Fix versions

Affects versions

git tip

Priority

Medium