When application server is shut down it automatically suspends the execution of new jobs All jobs still in an active state will be canceled and put into a specific state listed in table 1. Therefore it is recommended that prior to a planned system shutdown you should suspend the execution of new jobs manually and wait till running jobs are finished.
When application server shut downs unexpectedly (e.g. because of electricity shortage) all jobs in an active state will be obviously terminated. On restart of the Application Server these ghost jobs will be cleaned up and put into the appropriate state as listed in table 1.
Status before system shutdown |
Status after restart of the system |
Pending |
Closed without execution at system shutdown |
Running |
Aborted at system shutdown |
Being paused |
Aborted at system shutdown |
Paused |
Aborted at system shutdown |
Table 1: Job states after a system shutdown