PipelineCLI does not update workflow status when workflow is stopped on GUI

[tram]

Dear all,

When I submit a workflow by PipelineCLI with -sync option, I can also monitor the execution of the workflow by using Pipeline GUI under Active Sessions. How ever, if I terminate the execution of the workflow on the GUI, the PipelincCLI process does not stop.

Does LONI server consider this case? Or it considers only two cases, workflow terminated due to an error or successfully completed.

The synchronization between PipelineCLI and its server gives how many execution status of the workflow?

Thank you all,

Tram.

[zliu]

Only one workflow is submitted, when you stop the workflow under GUI, the workflow stops and the CLI process should terminate. It seems like the CLI didn't get the status message and it will be fixed.

Thanks,
Zhizhong

[tram]

Hi Zhizhong,

Thank you for the quick reply.

I've just discovered that once the pipeline is submitted, PipelineCLI loses the synchronization with the DPS server. Even if when the pipeline has successfully finished execution.

Could you please have a look and fix it?

Thank you,
Tram

[zliu]

Hi Tram,

I just tried a simple workflow (1 module with /bin/ls command), and submitted via command line with -sync option, it works as expected.

$ java -cp Pipeline.jar ui.cli.Main -c=/path/login.xml -sync -execute /path/workflow/ls.pipe

Submitting /path/workflow/ls.pipe for execution...
Execution started. (Session ID: 4c7da77b4895)
Execution completed. (Session ID: 4c7da77b4895)
1 workflow successfully completed.

Are you submitting long running workflows? If so, could you try a simple workflow? Are you using wireless or unstable network?

Thanks,
Zhizhong

[tram]

Hi Zhizhong,

Here are results I received:

If I submit a workflow by PipelineCLI with -sync option, and at the same time monitor its execution under GUI, the Pipeline CLI loses the synchronization with DPS server. I guess that DPS server can keep synchronization for only one Pipeline client for each instance of a workflow. In this case, the client with GUI that I use for monitor.

Other wise, if I do not login to the Pipeline client GUI to monitor the active session, the PipelineCLI process stops as expected.

That can explain for my question in the first post of this topic that why the PipelineCLI does not stop when I stop the execution on GUI.

Could you please check it? If it is true, it is possible for DPS server having more than 1 Pipeline client instance for each workflow?

Thank you very much,
Tram

[zliu]

Hi Tram,

That's the case. For now it only support one client to connect to a running workflow at a given time. It will be fixed in the future.

Thanks,
Zhizhong