JobScheduler remains in the status stopping after restart

h1. Restart behaviour
If you restart the JobScheduler via startscript

 ./bin/jobscheduler.sh restart

or via JOC (Menu->'Terminate and restart').

Then the JobScheduler waits for all running job tasks.

Only when all tasks are completed, then the JobScheduler stops and starts.
Until then, the JobScheduler is the status "stopping".

You can restart the JobScheduler with a timeout (in seconds) via startscript

  ./bin/jobscheduler.sh command "<terminate restart='yes' timeout='60'/>"

or via JOC (Menu->'Terminate and restart within ~60s').

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. "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

 ./bin/jobscheduler.sh command "<modify_spooler cmd='abort_immediately_and_restart'/>"

or via JOC (Menu->'Abort immediately and restart').

Please avoid endless tasks!