At times, you may want to stop or pause the Kernel without stopping it as a service (if the Kernel is running as a service) or stopping it by pressing <Ctrl> + <C> from the console. In such cases, you can stop or even pause the Kernel from the GUI. When the Kernel is stopped or paused, no requests for new process flows are executed.
Process Flow Status when Kernel is Stopped
When the Kernel is stopped, the system does not accept any new process flow requests for triggering. It just completes the existing process flows that are running, and then shut down the Kernel.
Process Flow Status when Kernel is Paused
When the Kernel is paused, the system just completes the existing process flows that are running. However, it does not accept any new process flow requests for triggering. Additionally, it does not accept any waiting process flows that could be manual execution requests or those in the Queue Processor. When the Kernel is paused, the Queue Processor is also paused. It does not activate any process flows or escalate them from the waiting queue to ready queue. It just maintains them in the queue list.
The pausing of the Kernel pauses the scheduler too. It does not allow triggering of any process flows through any events except JMS and HTTP events. The pausing/resuming/stopping of Scheduler synchronizes with the pausing/resuming/stopping of the Kernel.
If sub processes are being executed with Call action when the Kernel is paused or stopped, then they need to be made recoverable with the Call action, when the process flow shuts down, as the parent process flow will not stop unless all child process flows are executed.
Following are the major subsections:
|Learn how to manage Kernel.|
|Introduces Scheduler concept, events managed by Scheduler, Scheduler related properties, and managing Scheduler.|