Versions Compared

Old Version 3

changes.mady.by.user Ana Gologan (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Jonathan Muse

Saved on

Key

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

Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here !

The Asynchronous runner is located in Managed Apps under Jira Administration

Thread Pool Configuration

 

There are various Various tasks that require running SIL SIL™ programs in the background. Some Certain examples include Power Actions for JIRA(former Blitz Action) plugin actions Actions™ for Jira app or Power Scripts for JIRA (formerly known as JJUPIN) gScripts™ for Jira gadget scripts. These tasks are run in a special thread pool.

 


Excerpt

Thread pool configuration is easy, however you must understand the implications of each parameter since they may affect the tasks that are run in the background.

 


With the 4.0 version, we have unified this thread pool across the pluginsapps, and now all the add-ons apps use the same thread pool; a previously . Previous consolidation happened at version 3.x. This is hugely important of high importance because now all the background tasks will be are placed in this thread pool - and only this. 

Image RemovedImage Added

To configure it , you must specify:

  • Threads - the number of running threads (number of SIL SIL™ scripts running in the same time).
  • Time to Live (TTL) - time to live (running time for a SIL SIL™ script). If you run a task that takes more than TTL configured, the script will end ends with no result.
  • Checkpoint Interval - interval to clean up the expired tasks (the SIL SIL™ scripts that exceeds the TTL configured). The pool is maintained by a watchdog thread, and the checkpoint interval determines the interval between checks.

 


Info
titleTips

The page will show shows also the maximal maximum task queue length and the current tasks that are running. If your number of threads is constantly under the the max reached queue length, consider increasing the thread pool size. 

If you run reporting tasks, that may gather data from multiple sources and take a long time to complete, please increase both the number of threads (if the pool is occupied with those tasks) and the TTL so that the tasks/results will not be removed prematurely too early from the queue.