[ 
http://opencast.jira.com/browse/MH-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32697#comment-32697
 ] 

Tobias Wunden edited comment on MH-9225 at 1/8/13 9:58 PM:
-----------------------------------------------------------

Looking at the 1.3 codebase I see exactly two ways of getting a workflow into 
PAUSED state:

1) calling the pause method on the rest endpoint, which seems unlikely (I am 
not aware of any service or ui that is using it)
2) returning WorkflowOperationResult.Action.PAUSE as the result of a workflow 
operation handler

This means that there would be a workflow operation in the workflow that is 
calling pause due to its workflow configuration (such as hold for trim) or due 
to a programmatic error. Next to the obvious ones like trimming, I am looking at

* ScheduleWorkflowOperationHandler
* CaptureWorkflowOperationHandler
* IngestWorkflowOperationHandler

all of which are used in case of a scheduled recording to represent the state 
of a recording while the recording is scheduled, ongoing on the capture agent 
or in ingest state. The capture agent will usually report back the capture 
state to the capture agent state service, leading the service to eventually 
udpate the workflow and move it to the next step. 

So the reason for a workflow suddenly going into "PAUSED" state may be that 
there is a conflict between the capture agent ingesting the recording, in which 
case the recording starts to be processed, and the capture agent state service 
that is "manually" moving the workflow forward (actually backward) at the same 
time, because this update routine is only running every once in a while.
                
      was (Author: twunden):
    Looking at the 1.3 codebase I see exactly two ways of getting a workflow 
into PAUSED state:

1) calling the pause method on the rest endpoint, which seems unlikely (I am 
not aware of any service or ui that is using it)
2) returning WorkflowOperationResult.Action.PAUSE as the result of a workflow 
operation handler

This means that there would be a workflow operation in the workflow that is 
calling pause due to its workflow configuration (such as hold for trim) or due 
to a programmatic error. Next to the obvious ones like trimming, I am looking at

* ScheduleWorkflowOperationHandler
* CaptureWorkflowOperationHandler
* IngestWorkflowOperationHandler

all of which are used in case of a scheduled recording to represent the state 
of a recording while the recording is scheduled, ongoing on the capture agent 
or in ingest state. The capture agent will usually report back the capture 
state to the capture admin, leading the capture admin to udpate the workflow 
and move it to the next step. 

So the reason for a workflow suddenly going into "PAUSED" state may be that 
there is a conflict between the capture agent ingesting the recording, in which 
case the recording starts to be processed, and the capture admin that is 
"manually" moving the workflow forward (actually backward) at the same time, 
because this update routine is only running every once in a while.
                  
> Workflows automatically go into hold state after inspect but resume 
> processing correctly with a nudge from the resume workflow endpoint
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MH-9225
>                 URL: http://opencast.jira.com/browse/MH-9225
>             Project: Matterhorn Project
>          Issue Type: Bug
>          Components: Administrative Tools
>    Affects Versions: 1.4, 1.3, 1.2
>            Reporter: Adam McKenzie
>            Assignee: Adam McKenzie
>            Priority: Critical
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to