HotSpot Java VM hung on 2.6 2.7 v9 machines when running hottest.jar
without error message.
To reproduce the bug, read the instruction at
/home/fhsu/testbase/hottest/readme.txt
all necessary file located at
/home/fhsu/testbase/hottest/hottest.jar
Also read following email for more information.
--------------------------------------------------------------------
Date: Mon, 26 Apr 1999 15:29:15 -0700 (PDT)
From: James McIlree <###@###.###>
Subject: Re: Please review fix for cloudscape deadlock problem
To: ###@###.###
MIME-Version: 1.0
Content-MD5: UUz13v3xliTCAIVVRtPe7w==
Both the 2.6 and the 2.7 process are trying to
go to a safepoint. The only unusual thing I noticed was
that both had exactly one thread in accept().
You can find the stack traces at:
(or see attachments)
/net/ghopper/LocalBuild/19525.stack
/net/ghopper/LocalBuild/20844.stack
without error message.
To reproduce the bug, read the instruction at
/home/fhsu/testbase/hottest/readme.txt
all necessary file located at
/home/fhsu/testbase/hottest/hottest.jar
Also read following email for more information.
--------------------------------------------------------------------
Date: Mon, 26 Apr 1999 15:29:15 -0700 (PDT)
From: James McIlree <###@###.###>
Subject: Re: Please review fix for cloudscape deadlock problem
To: ###@###.###
MIME-Version: 1.0
Content-MD5: UUz13v3xliTCAIVVRtPe7w==
Both the 2.6 and the 2.7 process are trying to
go to a safepoint. The only unusual thing I noticed was
that both had exactly one thread in accept().
You can find the stack traces at:
(or see attachments)
/net/ghopper/LocalBuild/19525.stack
/net/ghopper/LocalBuild/20844.stack