You are viewing a plain text version of this content. The canonical link for it is here.
Posted to droids-dev@incubator.apache.org by "Richard Frovarp (JIRA)" <ji...@apache.org> on 2010/02/15 19:11:27 UTC
[jira] Commented: (DROIDS-76) Inconsistent awaitTermination between
SequentialTaskMaster and MultiThreadedTaskMaster
[ https://issues.apache.org/jira/browse/DROIDS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833926#action_12833926 ]
Richard Frovarp commented on DROIDS-76:
---------------------------------------
Yeah, that would seem to fix the problem. I think some of the example code is going to need to changes as well. SimpleRuntime , SimpleWalkingDroid, and Cli all use 0. I actually discovered the problem when switching from Sequential to MultiThreaded in the SimpleRuntime code.
> Inconsistent awaitTermination between SequentialTaskMaster and MultiThreadedTaskMaster
> --------------------------------------------------------------------------------------
>
> Key: DROIDS-76
> URL: https://issues.apache.org/jira/browse/DROIDS-76
> Project: Droids
> Issue Type: Bug
> Components: core
> Reporter: Richard Frovarp
> Priority: Minor
> Attachments: SecuentialTaskMaster.patch
>
>
> awaitTermination with a timeout of 0 has inconsistent behavior between SequentialTaskMaster and MultiThreadedTaskMaster. MultiThreadedTaskmaster times out immediately with zero due to how it uses ThreadPoolExecuter. SequentialTaskMaster has an unlimited timeout with a value of zero. SequentialTaskMaster should probably be the one changed. The example code probably needs to be changed as a result as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.