What is the relationship between the adapter thread count and the MaxTask MTS parameters on the SIEBEL side?
Article ID: KB0089318
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel | - |
| Not Applicable | - |
Description
Resolution:
Here is the description from Oracle for the two parameters:
-----------------------------------------------------------------------------------------------------------------
Maximum MT Servers: This is the maximum number of multithreaded Siebel Server processes to be run concurrently for a component that has multithreading enabled. The number of tasks that may run in each Siebel Server process is determined by the value of the Maximum Tasks parameter divided by Maximum MT Servers. Increase or decrease this value based on the number of users for the given component process.
Maximum Tasks:The maximum number of background mode, batch mode, or interactive mode processes or threads that may run concurrently for a component. This value applies to threads for components that have multithreading enabled, or otherwise component processes. You should increase or decrease this value based on the number of users for the given component process.
---------------------------------------------------------------------------------------------------------
The number of connections (i.e. the connection pool size) to Siebel is determined based upon the number of threads defined in the adapter. Make sure that the connection pool size configured for the Siebel adapter is less than the Maximum Tasks value.
As per the tests conducted with MT Server and Maximum tasks, there are two observations.
1). If MT server and Max task are defined, the number of connections opened to Siebel, assuming no delays, should be less than (Maximum Tasks/ MT server). Otherwise, the adapter will throw a JDB exception.
2). Sometime there may be a delay in creating the connections in the adapter. If there is a delay the adapter can still successfully create a number of connections larger than the (Maximum Tasks/ MT server), assuming the MT Server > 1.
As per the two parameters interpretation from the Oracle documentation and the test results, it is recommended to configure the connection pool size for each adapter instance less than (Maximum Tasks/ MT server).
Here is the description from Oracle for the two parameters:
-----------------------------------------------------------------------------------------------------------------
Maximum MT Servers: This is the maximum number of multithreaded Siebel Server processes to be run concurrently for a component that has multithreading enabled. The number of tasks that may run in each Siebel Server process is determined by the value of the Maximum Tasks parameter divided by Maximum MT Servers. Increase or decrease this value based on the number of users for the given component process.
Maximum Tasks:The maximum number of background mode, batch mode, or interactive mode processes or threads that may run concurrently for a component. This value applies to threads for components that have multithreading enabled, or otherwise component processes. You should increase or decrease this value based on the number of users for the given component process.
---------------------------------------------------------------------------------------------------------
The number of connections (i.e. the connection pool size) to Siebel is determined based upon the number of threads defined in the adapter. Make sure that the connection pool size configured for the Siebel adapter is less than the Maximum Tasks value.
As per the tests conducted with MT Server and Maximum tasks, there are two observations.
1). If MT server and Max task are defined, the number of connections opened to Siebel, assuming no delays, should be less than (Maximum Tasks/ MT server). Otherwise, the adapter will throw a JDB exception.
2). Sometime there may be a delay in creating the connections in the adapter. If there is a delay the adapter can still successfully create a number of connections larger than the (Maximum Tasks/ MT server), assuming the MT Server > 1.
As per the two parameters interpretation from the Oracle documentation and the test results, it is recommended to configure the connection pool size for each adapter instance less than (Maximum Tasks/ MT server).
Issue/Introduction
What is the relationship between the adapter thread count and the MaxTask MTS parameters on the SIEBEL side?
Feedback
Yes
No
Powered by
