You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@harmony.apache.org by "weldon washburn (JIRA)" <ji...@apache.org> on 2007/02/16 22:22:05 UTC

[jira] Assigned: (HARMONY-3144) [drlvm][thread] Stopping unborn thread has no effect

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

weldon washburn reassigned HARMONY-3144:
----------------------------------------

    Assignee: weldon washburn

> [drlvm][thread] Stopping unborn thread has no effect
> ----------------------------------------------------
>
>                 Key: HARMONY-3144
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3144
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Salikh Zakirov
>         Assigned To: weldon washburn
>            Priority: Minor
>         Attachments: StopUnborn.java
>
>
> Stopping a thread that have not been started yet should cause a thread be terminated immediately upon start(), according to the Thread.stop() specification:
>         It is permitted to stop a thread that has not yet been started. If the thread is eventually started, it immediately terminates.
> Attached test StopUnborn.java demonstrates this behaviour.
> Surprisingly, other JVMs also exhibit incorrect behaviour (ibm vme, bea, sun).

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