RR, M 7186723: TEST_BUG: Race condition in sun/management/jmxremote/startstop/JMXStartStopTest.sh

Dmitry Samersoff Dmitry.Samersoff at oracle.com
Sat Aug 25 13:16:19 PDT 2012


Alan,

On 2012-08-26 00:00, Alan Bateman wrote:
> On 25/08/2012 16:18, Dmitry Samersoff wrote:
>> Hi Everybody,
>>
>> Test was changed to better support windows.
>>
>> http://cr.openjdk.java.net/~dsamersoff/7186723/webrev.01/
>>
>> -Dmitry
>>
> You will also need to remove the test from the exclude
> (jdk/test/ProblemList.txt), we had to add it because it was causing the
> jdk_management target to hang Windows systems.

Thank you! I'll change it.

> I haven't reviewed the changes proposed here but I did skim
> JMXStartStopDoSomething and just wonder if the busy code is necessary. I
> would have thought that such a test could control a slave process via a
> socket connection or other means.

The test sends couple of jcmd commands to the single server process.
jcmd do attach, call, detach for each command. So I have to keep server
running for some time.

 Server process with just while(true) sleep(1); would run forever if
test  doesn't kill it for some reason - it's why I use busy code.

So I'm open for any advice here.

-Dmitry


-- 
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...




More information about the serviceability-dev mailing list