You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Sheryl John (Commented) (JIRA)" <ji...@apache.org> on 2011/10/08 09:29:29 UTC
[jira] [Commented] (OODT-203) Create a Non-Blocking threaded
implementation of the Workflow Engine
[ https://issues.apache.org/jira/browse/OODT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123401#comment-13123401 ]
Sheryl John commented on OODT-203:
----------------------------------
Hi,
I have a few of questions here:
1.Has the NonBlockingThreadPoolWorkflowEngine implementation been updated after the initial one?
I went through the code from the checked out version around r1156658 of OODT 0.4 and it looks just as it is described by David's comment.
2. In the above comment, which higher level file manager services are you referring for modeling the unit test?
3. By the PEATE example, do you mean the case described in OODT-202?
4. How will AbstractBaseWorkflowEngine be different from the current core WorkflowEngine? Are you thinking of adding some new functionality to the existing ones?
> Create a Non-Blocking threaded implementation of the Workflow Engine
> --------------------------------------------------------------------
>
> Key: OODT-203
> URL: https://issues.apache.org/jira/browse/OODT-203
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Environment: from JPL's last internal WM JIRA release
> Reporter: David Woollard
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
>
> The current implementation of the threaded workflow engine uses a thread from its thread pool for each of the workflows it creates. This can cause a problem if a significant number of workflows submitted block waiting on preconditions to be satisfied. Each of these paused workflows hangs on to the thread allocated from the thread pool, so workflows that could be run are blocked by workflows waiting on preconditions if the thread pool is fully allocated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira