What is the behavior of checkpoints with the respect to called processes (spawn and not spawn)

book

Article ID: KB0091376

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Resolution:
Case 1 –

Main process has a checkpoint after a call process (spawned)  is called.

Results: Two jobs were created: 1- for main process 2- for Spawn process.
Main process jobs were checkpointed but not jobs from spawn process.


Case 2 –

Checkpoint is taken in subprocess (spawn). No checkpoint in Main process.

Results: Two jobs were created: 1- for main process 2- for Spawn process.
Subprocess jobs were checkpointed not main process jobs.

Case 2- Check point is taken in either a main or a subprocess (not spawn) then
the state of both processes is saved when a checkpoint is taken.

This is an expected behavior and document mentioned it too. Refer to your reference guide/ Checkpoint.

When a checkpoint occurs in a called process, the checkpoint saves the state of the current process instance. If no called processes spawn new process instances, then a checkpoint in any called process saves the state of the process instance, including state from the parent process(es) of the current process. In the case of a called process that spawns a new process instance, only the spawned process instance is saved.

Issue/Introduction

What is the behavior of checkpoints with the respect to called processes (spawn and not spawn)