Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Download: kill_tasks.zip
    • The files included should be usable with Windows and Unix systems.
  • Create a folder issues within the ./config/live folder of your JobScheduler installation.
  • Extract the archive to the folder issues. The archive will extract the files included to a folder kill_tasks, therefore all objects will be located in the ./config/live/issues/kill_tasks folder. 
  • You can store the sample files to a different folder, however, you would have to adjust the job_chains parameter from the kill_tasks order, see below.

Components

  • The test chain run_infinitely: this chain implements a test job that runs infinitely and can be started in multiple instances
    • One job run_infinitely is included that executes a number of ping commands to simulate a long running job. The job is configured to run in multiple instances if more than one order is active for the job chain.
    • One order run_infinitely is included that starts the run_infinitely job chain. This order can be started manually by use of JOC. Additional orders can be added by use of the Add Order context menu item with JOC.
  • The kill chain kill_tasks_in_job_chain: this chain implements the killing of tasks for any job chains
    • One job kill_tasks_in_job_chain is included that implements the JobScheduler <kill_task> XML command.
    • One order kill_tasks_in_job_chain is included that starts the kill_tasks_in_job_chain job chain. This order can be started manually by use of JOC.
      • This order makes use of two possible parameters:
        • job_chains: This parameters accepts one or multiple job chain paths. 
          • Specify the full path including all folder names of the job chain that runs tasks that should be terminated.
          • Separate multiple job chain paths by use of a semicolon ";".
        • timeout: This parameter is available for Unix systems only and specifies a timeout in seconds. 
          • The job kill_tasks_in_job_chain will first send a SIGTERM signal to any tasks of the run_infinitely job. 
          • Should the run_infinitely job not be terminated after the timeout expires then a SIGKILL signal is sent to the tasks.

...