[jira] Updated: (WICKET-1181) Task does not deal very well with a terminated thread

["Frank Bille Jensen (JIRA)" <ji...@apache.org>]

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

Frank Bille Jensen updated WICKET-1181:
---------------------------------------

    Fix Version/s:     (was: 1.3.0-rc3)
                   1.3.0-final

> Task does not deal very well with a terminated thread
> -----------------------------------------------------
>
>                 Key: WICKET-1181
>                 URL: https://issues.apache.org/jira/browse/WICKET-1181
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-rc1
>            Reporter: Stephane Bailliez
>            Priority: Minor
>             Fix For: 1.3.0-final
>
>
> For some weird reason, several time I was looking for a reason why wicket did not pickup the changes in resources through the modification watcher and why it was not stopping at all even in the run code... as I noticed the thread was terminated (for an unknown reason, the uncaughtexceptionhandler is only java5)
> The task cannot figure itself whether the thread is really started or not.
> Rather than using isStarted flag which is static after it is set, I would also Thread.getState() to figure out whether it is active or not

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