[
https://issues.apache.org/jira/browse/OODT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051621#comment-13051621
]
Chris A. Mattmann commented on OODT-203:
----------------------------------------
Since OODT-202 was filed, I would recommend the following things in order to
close this issue:
1. reproducible unit tests that demonstrate that OODT-202 isn't happening
anymore. These can be modeled after the single JVM unit tests of higher level
file manager services. These should create a sequence of 4 or so workflows akin
to PEATE example provided by [~bfoster].
2. as [~woollard] mentioned, this was an initial version – ideally we would
probably make some methods protected and turn the core WorkflowEngine into an
AbstractBaseWorkflowEngine that provides functionality that both
ThreadPoolWorkflowEngine and NonBlockingThreadPoolWorkflowEngine can inherit
from.
> 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: Bug
> Components: workflow manager
> Environment: from JPL's last internal WM JIRA release
> Reporter: David Woollard
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
