You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexander N. Alexeev (JIRA)" <ji...@apache.org> on 2007/10/08 15:11:50 UTC
[jira] Created: (HARMONY-4905) Thread's state after Join invocation
is debatable
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
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.
[jira] Updated: (HARMONY-4905) [drlvm][thread] Last thread event
before stick in Join is incorrect
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky updated HARMONY-4905:
---------------------------------------
Summary: [drlvm][thread] Last thread event before stick in Join is incorrect (was: Last thread event before stick in Join is incorrect)
> [drlvm][thread] Last thread event before stick in Join is incorrect
> -------------------------------------------------------------------
>
> Key: HARMONY-4905
> URL: https://issues.apache.org/jira/browse/HARMONY-4905
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows XP
> Reporter: Alexander N. Alexeev
> Attachments: event_log.txt, 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.
> Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4905) Last thread event before stick in
Join is incorrect
Posted by "Alexander N. Alexeev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander N. Alexeev updated HARMONY-4905:
------------------------------------------
Attachment: event_log.txt
sample event trace in which problem can be seen
> Last thread event before stick in Join is incorrect
> ---------------------------------------------------
>
> Key: HARMONY-4905
> URL: https://issues.apache.org/jira/browse/HARMONY-4905
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows XP
> Reporter: Alexander N. Alexeev
> Attachments: event_log.txt, 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.
> Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-4905) [drlvm][thread] Last thread event
before stick in Join is incorrect
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-4905.
--------------------------------------
Resolution: Fixed
Assignee: Gregory Shimansky
Ok closing the bug according to evaluation.
> [drlvm][thread] Last thread event before stick in Join is incorrect
> -------------------------------------------------------------------
>
> Key: HARMONY-4905
> URL: https://issues.apache.org/jira/browse/HARMONY-4905
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows XP
> Reporter: Alexander N. Alexeev
> Assignee: Gregory Shimansky
> Attachments: event_log.txt, 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.
> Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-4905) [drlvm][thread] Last thread event
before stick in Join is incorrect
Posted by "Pavel Rebriy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553288 ]
Pavel Rebriy commented on HARMONY-4905:
---------------------------------------
The issue is fixed after HARMONY-3267 and HARMONY-5164 commits.
I think the bug could be closed.
> [drlvm][thread] Last thread event before stick in Join is incorrect
> -------------------------------------------------------------------
>
> Key: HARMONY-4905
> URL: https://issues.apache.org/jira/browse/HARMONY-4905
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows XP
> Reporter: Alexander N. Alexeev
> Attachments: event_log.txt, 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.
> Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4905) Last thread event before stick in
Join is incorrect
Posted by "Alexander N. Alexeev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander N. Alexeev updated HARMONY-4905:
------------------------------------------
Description:
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.
Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
was:
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.
Issue Type: Bug (was: Test)
Summary: Last thread event before stick in Join is incorrect (was: Thread's state after Join invocation is debatable)
> Last thread event before stick in Join is incorrect
> ---------------------------------------------------
>
> Key: HARMONY-4905
> URL: https://issues.apache.org/jira/browse/HARMONY-4905
> Project: Harmony
> Issue Type: Bug
> 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.
> Events sequence can be seen at attached event_log.txt, place in trace where Join happens is marked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4905) Thread's state after Join invocation
is debatable
Posted by "Alexander N. Alexeev (JIRA)" <ji...@apache.org>.
[ 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.