Please enable JavaScript to view this site.

Altova FlowForce Server 2020 Advanced Edition

Queue settings enable you to control usage of server resources, for example, by limiting the number of instances running in parallel for each job. In order to change queue settings, your user account must have the "Define execution queues" privilege, see How Privileges Work.


Queue settings

Select existing queue

Select this option if you want to assign the job to a standalone, external queue defined previously, see Setting up Distributed Execution.

Minimum time between runs

An execution queue provides execution slots, where the number of available slots is governed by the "maximum parallel runs" setting multiplied by the number of workers assigned according to the currently active rule. Each slot will execute job instances sequentially.


The "Minimum time between runs" setting keeps a slot marked as occupied for a short duration after a job instance has finished, so it will not pick up the next job instance right away. This reduces maximum throughput for this execution queue, but provides CPU time for other execution queues and other processes on the same machine.

Maximum parallel runs

This option defines the number of execution slots available on the queue. Each slot executes job instances sequentially, so the setting determines how many instances of the same job may be executed in parallel in the current queue. Note, however, that the number of instances you allow to run in parallel will compete over available machine resources. Increasing this value could be acceptable for queues that process "lightweight" jobs that do not perform intensive I/O operations or need significant CPU time. The default setting 1 is the most conservative and is suitable for queues that process resource-intensive jobs (so as to ensure only one such "heavyweight" job instance is processed at a time).


This option does not affect the number of maximum parallel HTTP requests accepted by FlowForce Server (such as those from clients that invoke jobs exposed as Web services). For details, see Reconfiguring FlowForce Server pool threads.


If you are testing parallel service execution from your browser, be aware that the browser may hold back additional requests that address the same URL. As a workaround, you can initiate parallel instances of the same job from two different browsers.

© 2020 Altova GmbH