Details
-
Feature
-
Status: Released (View Workflow)
-
High
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- When users suspend orders then the instruction that is currently executed will continue. When the instruction is completed the order will be suspended.
- The behavior is intended not to interrupt instructions that are in execution. For example, a job should complete before suspending the order.
- For use with Shell jobs and with JVM jobs the option is offered to kill a running job. The option considers Grace Timeout settings for jobs before the order is suspended.
- When suspending orders they are marked for suspension while the current instruction is executed. This is indicated from an order state qualifier such as waiting/suspending, running/suspending etc.
Desired Behavior
- Users wish to find an option to reset any instruction that is currently executed for an order and to immediately suspend the order:
- For the Job Instruction
- the job will be killed which corresponds to use of suspend/terminate task.
the order will stop waiting for a Job Admission Time. See JS-2168
- For the Retry Instruction the current delay and remaining number of tries are discarded.
- For the Sleep Instruction the remaining duration is discarded.
- Orders waiting with the ExpectNotices Instruction or ConsumeNotices Instruction will stop waiting for a Notice.
- Orders waiting with a Cycle Instruction will stop waiting for the next interval. Orders executing instructions inside a Cycle Instruction will be suspended with the related instruction.
- Orders waiting with the Lock Instruction will stop waiting for the resource.
- For the Job Instruction
- When orders are resumed after a suspend/abort operation then
- the Retry Instruction will be resumed from the first try and first delay .
- the Sleep Instruction will be executed for the duration specified.