Specifying maxConcurrentQueuedTransactions sets the maximum number of queued transactions that may be processed simultaneously by the Subproceso de Arbortext PE 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 Subproceso de Arbortext PE pool will execute as many queued transactions as it can by keeping all Subprocesos de Arbortext PE busy.

If it’s set to 0, no queued transactions will be accepted by the Subproceso de Arbortext PE 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.