• Sign In
  1. Messages

restarting task progression after remote task

LabKey Support Forum (Inactive)

View Message

view list print
restarting task progression after remote task wnels2  2009-11-02 11:11
Status: Closed
 
I've added a task to the pipeline that runs remotely, its location name is cloud. I've added a Mule service that listens for the Cloud task's complete message and runs the org.labkey.pipeline.mule.StatusRequestHandler. This appears to work and the complete status is written to the database but the the progression never starts up again. The PipelineJob.runStateMachine returns false when the task is not local.
How does the next task get put on ActiveMQ?

Thanks,
Bill
 
 
wnels2 responded:  2009-11-04 06:59
Okay, now I see the difference between the task runner and job runner in the Mule configs.
I'm going to try to get the jobStore from the statusfiles when the complete message comes in from SQS and submit it to the stateMachine in order to continue the task progression. Does this sound reasonable?
Thanks,
Bill
 
wnels2 responded:  2009-11-04 09:09
It appears to be working. Probably should test a little more though.
Thanks,
Bill
 
jeckels responded:  2009-11-05 09:47
Hi Bill,

Sorry to be slow to respond. You might want to check out org.labkey.pipeline.mule.PipelineJobRunnerGlobus and org.labkey.pipeline.mule.GlobusListener. It sounds like they do something very similar to what you want - they submit a job to Globus, wait for it to complete, and then continue processing with the rest of the tasks. In particular, PipelineJobRunnerGlobus.updateStatus() may be quite relevant.

Thanks,
Josh