Gateway Needs To Be Restarted After Component Reaches Max Tasks
(Doc ID 1225343.1)
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 188.8.131.52  and later
Information in this document applies to any platform.
It is Siebel version 184.108.40.206 . They are using Oracle RAC server v 10g.
Customer is using eProdCfgObjMgr_enu along with Java Data Bean.
For this OM max tasks/Max MT was set to 20:1.
***Checked for relevance on 04-Oct-2013***
When their Oracle RAC server failover happens and come back online ( from logs it seems it takes about 4-8 secs), these java data bean OM tasks hung and then this OM runs out of tasks. Then no one can login until they restart gateway. The Siebel application is not accessed through the Siebel UI, it is using java databean. One button click would generate a request that in turn would translate into a Siebel task.They only see 2-4 Siebel tasks in average
So the issue is the gtway server doesn't update status since MaxTasks is reached on OM (product configurator), so another MTServer is not released to accept server requests since that same MT Server is being used.
We see error in OM logs as follows:
SBL-SMI-00114: The Multithreaded Server ha
s reached the maximum number of concurrent tasks ((null)) connection:7a4
We suggested customer to test with following settings but it DID NOT help only delayed the issue being happening in their environment.
Max/Min MT = 5
SISNAPI connidle time=320
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|