About Thread Pooling for Siebel Application Object Manager

The pool size per multithreaded process for a Siebel Application Object Manager is determined by the combined settings of the parameters UseThreadPool, ThreadAffinity, MinPoolThreads, and MaxPoolThreads.

Siebel Application Object Manager thread pooling reduces some of the system resource usage devoted to creating and closing session threads, as users log in and log out or are timed out. As when you are not using thread pooling, session threads are created as needed as session requests demand. However, instead of being closed when a session terminates, they are released to a pool, where they become available for use by a subsequent session.

When ThreadAffinity is FALSE (the default), threads are multiplexed, as can be done with certain types of database connections or SISNAPI connections. At any given time, each thread can be dedicated to one or more user session (task).

Note: Using thread pooling introduces its own overhead, such as in task context-switching. For this reason, it is strongly recommended not to try to pool threads without also multiplexing them. That is, do not set both UseThreadPool and ThreadAffinity to TRUE.