The Transaction Threads tab of the StarSQL Resource Manager Properties dialog allows you to control how many threads are available for concurrent indoubt transactions. There can be only as many concurrent indoubt transactions as there are threads configured. For example, if you set the maximum to 10, then only 10 transactions can be in an indoubt state at the same time, and the Resource Manager queues any other transactions that attempt to enter the indoubt state. Set the Maximum Number of Threads to 0 (zero) if you do not want to limit the number of concurrent transactions that can be in the indoubt state.
The Resource Manager keeps the minimum number of threads available and dynamically increases the number of threads as they are needed, up to the maximum number of threads specified. When a thread is no longer needed, the Idle Thread Timeout period determines how quickly the thread is released. The default timeout period is 180 seconds.
If you change any of the Resource Manager properties, you must restart the service for the new properties to take affect.