[
https://issues.apache.org/jira/browse/PIVOT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Volkert resolved PIVOT-76.
-------------------------------
Resolution: Fixed
> Threading issues with ApplicationContext$ScheduledCallback
> ----------------------------------------------------------
>
> Key: PIVOT-76
> URL: https://issues.apache.org/jira/browse/PIVOT-76
> Project: Pivot
> Issue Type: Bug
> Components: wtk
> Affects Versions: 1.1
> Reporter: Todd Volkert
> Assignee: Todd Volkert
> Fix For: 1.2
>
>
> ApplicationContext$ScheduledCallback extends TimerTask and queues a runnable
> on the UI thread when the timer task is called to run. This presents a
> threading problem: the timer task may be called to run (on the Timer thread)
> while the underlying runnable is running on the UI thread. In this case, the
> underlying runnable may call cancel() on the timer task, but since the timer
> task is currently running, the underlying runnable will be re-queued on the
> UI thread, meaning that it will get called to run after the timer task has
> been cancelled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
