You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Salikh Zakirov (JIRA)" <ji...@apache.org> on 2007/02/08 17:22:05 UTC
[jira] Created: (HARMONY-3144) [drlvm][thread] Stopping unborn
thread has no effect
[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
Priority: Minor
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.
[jira] Assigned: (HARMONY-3144) [drlvm][thread] Stopping unborn
thread has no effect
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (HARMONY-3144) [drlvm][thread] Stopping unborn
thread has no effect
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn closed HARMONY-3144.
------------------------------------
Resolution: Won't Fix
since drlvm behaves in the same way as the commercial implementations, there is no reason to "fix" something. Thus the rationale for, "won't fix"
> [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.
[jira] Updated: (HARMONY-3144) [drlvm][thread] Stopping unborn
thread has no effect
Posted by "Salikh Zakirov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Salikh Zakirov updated HARMONY-3144:
------------------------------------
Attachment: StopUnborn.java
> [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
> 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.