idle_timeout for task termination should be considered for use on Agents with an Open Source License

Current Situation

1. Users can run any sequence of Shell Jobs in a job chain on an Agent with the Open Source license.
2. When job types are used that include to load a Java Virtual Machine as e.g. Java Jobs, JavaScript Jobs, PowerShell Jobs, then the unloading of the Java Virtual Machine at the end of a task is delayed for 5s.
   • This is an optimization that is intended to re-use the same task if additional orders would arrive in short intervals.
   • However, this feature causes a task for your first job to be terminated with a delay and your next job in the job chain that requires a task start then hits the limit of parallel tasks.
   • The same problem occurs for Shell Jobs 1) that use a monitor script as such scripts are implemented in languages as in 2) that load a JVM.

Test Cases

• From the attached archive consider the job chains
  • shell_job_chain1
    • Two shell jobs are running successfully in sequence on an Agent.
    • Test case is successful
  • shell_monitor_job_chain1
    • Two shell jobs with scripted monitors (powershell) are running in sequence on an Agent. Both jobs use idle_timeout=0. The second job is not executed due to license restrictions.
    • test cails fails
  • powershell_job_chain1
    • One powershell job on an Agent, a shell job on a Master and another PowerShell job on an Agent are running in sequence. Both PowerShell jobs use idle_timeout=0.
    • Test case is successful
    • Test case fails if the shell job that runs on the Master is removed