In this dialog you can configure the behaviour with multiple concurrently running jobs. A job is some larger task which the server must handle like rendering a report (i-net Clear Reports) or comparing two documents (i-net PDFC).

The server has internal mechanisms to avoid low memory (RAM) situations when executing multiple jobs. For that the server can pause some job so it frees used memory. The job will be continued later. Nevertheless errors due to low memory (OutOfMemory errors) may still occur.

The following settings do not help in case of memory problems with one single large job like one big report or comparison!

The number of concurrently running jobs. Additional jobs are queued. A larger value needs more resources like memory and CPU but can give users a better response time.

• Default value: Is determined from available CPUs and Memory of the server (application specific)

When a job was paused by the server it waits some time for more memory to become available before the next job is paused. This sets how long the server waits at least. One job always stays active.

Due to errors from different sources it may happen that a job is no longer continuing its execution and is not stopping or failing. To prevent those jobs from blocking the server they are canceled automatically if they do not make any progress in the set period of time.

There is no special handling for paused jobs: a job paused for the set amount of time will be canceled.

• Default value: 1 hour
• The value 0 causes jobs never to be canceled

In rare cases is may happen that a job does not respond to a cancelation signal. It may be blocked or too busy to react. When a job is being canceled for the set period of time then it will be removed/terminated if possible.

It makes no difference whether the job was canceled by a user action or automatically by timeout (see above).

• Default value: 5 minutes
• The value 0 causes jobs never to be terminated