Specifying maxConcurrentQueuedTransactions sets the maximum number of queued transactions that may be processed simultaneously by the Arbortext PE sub-process pool.

There are two other possible values, -1 and 0.

If it’s set to -1, the default, there is no specified limit, and the Arbortext PE sub-process pool will execute as many queued transactions as it can by keeping all Arbortext PE sub-processes busy.

If it’s set to 0, no queued transactions will be accepted by the Arbortext PE sub-process pool, effectively reserving the entire pool for immediate transactions only. If you need to reserve a Sub-process pool for queued requests, refer to Specifying a Dedicated Queuing Pool.