| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Restart behaviour
If you restart the JobScheduler via startscript
...
In this case the JobScheduler waits only 60 seconds.
All tasks which are still running after 60 seconds are aborted with an exit code 99.
So each job of these tasks will be stopped, except the job is configured with stop_on_erroh1. error="no".
Note that the timeout for terminate in JOC is configurable in the ./config/operations_gui/custom.js (see also here).
JobScheduler remains in the status stopping
...
If you have an endless task then the JobScheduler remains endless in the status "stopping" after restart.
In this case you must abort and restart the JobScheduler via startscript
...