harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1789) [DRLVM] Race condition between Thread.interrupt and Object.wait, Thread.sleep or join
Date Fri, 17 Nov 2006 08:07:41 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1789?page=comments#action_12450658 ] 
Alexey Varlamov commented on HARMONY-1789:

Here is what I found on multicore Linux machine (SUSE9 2xXeon):
1) The HARMONY1789 hangs with pure H-1789-update.patch, the same as it does with original
Nikolay's patch. Good news is that HARMONY-2217 patches (#1 actually) fixes this hang. 
2) All the patches do not improve run statistics on the mntioned machine :(. In fact BEA behaves
equally badly, typical picture:
1000 interrupts generated
225 interrupts received, 84 polled, 141 exceptions
Clearly the test is inherently unstable and is not really suitable for multicore systems...
I've been lucky to get similar picture even on my Win laptop on BEA, but only once; next ~500
runs passed.
3) Nikolay claimed [1] that this patch should solve hanging ThreadTest of classlib - but it
does not. However this may be unrelated problem, I do not consider it as blocker for this
[1] http://issues.apache.org/jira/browse/HARMONY-1974#action_12449458

Generally I agree that this series of patches improves code a lot; will test it a bit more
and commit if nothing alarming happened.

> [DRLVM] Race condition between Thread.interrupt and Object.wait, Thread.sleep or join
> -------------------------------------------------------------------------------------
>                 Key: HARMONY-1789
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1789
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Nikolay Kuznetsov
>         Assigned To: Alexey Varlamov
>         Attachments: H-1789-updated.patch, H-1789.patch, HARMONY1789.java, Test.java
> According to the specification wait/join or sleep methods should check if thread was
interrupted before entering wait. DRLVM hythread implmentation do checks interrupted status(see
hythread condition implmentation), however thread may be interrupted just after the status
was checked and before entering condition wait. Thus it's required to ensure that waiting
state will be reached having interrupted status unchanged.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message