You can configure queue parameter max-concurrent-transactions to limit the number of transactions from a single queue that can be performed simultaneously. If max-concurrent-transactions is omitted, it defaults to 0, which means there is no limit. After the number of transactions set by this parameter have started executing, the Arbortext Queue will not present another transaction to the Queued Transaction Scheduler for execution until one of the executing transactions completes.