To Specify Advanced Transaction Processing Settings

1. Enter the desired number of Worker Threads (default 100).

   This is the number of threads used to process transactions. This value limits the number of transactions that are processed concurrently. These threads are statically allocated at startup.

   ---

   Note –

   When the Worker Threads setting is changed, you must restart all running Identity Manager instances for the change to take effect.

   ---

2. Enter the desired Lease Duration (ms) (default 600000).

   This controls how long a server locks a transaction that it is retrying. The lease is renewed as needed. However, if the server does not shutdown cleanly, then another server is not able to lock the transaction until the original server’s lease expires. The value should be at least one minute. Setting the value smaller can impact the load on the Transaction Persistent Store.

3. Enter the Lease Renewal (ms) time (default 300000).

   This controls when the lease of a locked transaction is renewed. It is renewed when there are this many milliseconds remaining on the lease.

4. Enter the time to Retain Completed Transactions in Store (ms) (default 360000).

   How many milliseconds to wait before removing completed transactions from the Transaction Persistent Store. Unless transactions are configured to be immediately persisted, the Transaction Persistent Store does not contain all completed transactions.

5. Enter the Ready Queue Low Water Mark (default 400).

   When the transaction scheduler’s queue of ready-to-run transactions falls below this limit, it refills the queue with any available ready-to-run transactions up to the high water limit.

6. Enter the Ready Queue High Water Mark (default 800).

   When the transaction scheduler’s queue of ready-to-run transactions falls below the low water mark, it refills the queue with any available ready-to-run transactions up to this limit.

7. Enter the Pending Queue Low Water Mark (default 2000).

   The transaction scheduler’s pending queue holds failed transactions that are pending a retry. If the size of the queue exceeds the high water mark, then all transactions beyond the low water mark, are flushed to the Transaction Persistent Store.

8. Enter the Pending Queue High Water Mark (default 2000).

   The transaction scheduler’s pending queue holds failed transactions that are pending a retry. If the size of the queue exceeds the high water mark, then all transactions beyond the low water mark, are flushed to the Transaction Persistent Store.

9. Enter the Scheduler Period (ms) (default 500).

   This is how often the transaction scheduler should run. When it runs, the transaction scheduler moves ready-to-run transactions from the pending queue to the ready queue, and performs other periodic duties such as persisting transactions to the Transaction Persistent Store.

10. Click Save to accept the settings.