harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander N. Alexeev (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4905) Thread's state after Join invocation is debatable
Date Mon, 08 Oct 2007 13:24:50 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander N. Alexeev updated HARMONY-4905:
------------------------------------------

    Attachment: pack.zip

Testcase shows that last event for "main" thread before hanging in join is MonitorContendedEnter.

> Thread's state after Join invocation is debatable
> -------------------------------------------------
>
>                 Key: HARMONY-4905
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4905
>             Project: Harmony
>          Issue Type: Test
>          Components: DRLVM
>         Environment: Windows XP
>            Reporter: Alexander N. Alexeev
>         Attachments: pack.zip
>
>
> When one thread spawns another and joins it, waiting for its
> termination, it becomes blocked on monitor  (from last handled event
> JVMTI_EVENT_MONITOR_CONTENDED_ENTER for that thread before 'sleep") ,
> while in other VMs (Sun's, IBM's and BEA's) thread which calls "Join"
> starts waiting (last event is JVMTI_EVENT_MONITOR_WAIT before
> 'sleep"). Probably set of events depends on VM internals, but in
> common sense "waited" state is more suitable for thread which waits
> for other thread termination.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message