[
https://issues.apache.org/jira/browse/OODT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124722#comment-13124722
]
Sheryl John commented on OODT-203:
----------------------------------
Thank you for your answers, Chris.
So for the workflow manager unit tests, we should test a XmlRpcWorkflowManager
client to run some workflows with predefined tasks,conditions,metadata etc
right?
Before I start, I wanted to confirm if I should define some test
workflows/tasks files like the test.txt and met files that were used to test
the ingestion in the XmlRpcFileManager unit tests.
> 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
