Pipeline execution timeout
I have subpipelines started via the Pipeline Execute snap in a parent that runs continuously (not Ultra) as a listener. There may be long periods of no documents flowing through the parent to the sub...
Forum Discussion
This sounds like a bug, the snap should not be failing like this. We’re going to take a look at it.
How are you keeping the pipeline running continuously? The safest approach would be to have the snap that is keeping the pipeline alive finish after some amount of time and then start up another execution.
The pipeline has a continuous JMS listener that keeps it executing. Its on a scheduled task so that if it happens to stop it starts up again right away. I can’t set the pipeline or task to stop after a certain period of time, correct? I would have to create another pipeline to monitor other pipeline executions, correct?
Ah, I was hoping the JMSConsumer had a timeout. It does have a ‘Control Destination’ that I think you can use to stop it.
The ability to stop a scheduled task after a period of time was added in the 4.10 release (see the tasks page). Be aware that stopping a pipeline is a pretty harsh operation, any snaps that are actively working will be interrupted and you might lose data.
Thanks, I will look into the Control Destination.
Ultimately I think the best solution would be if the DB snaps re-connected upon a connection timeout instead of erroring out. Do you know if that is a near-future enhancement?
