SBL-SMI-00064: Internal: Multi-threaded server for component %1 got a request for component %2

Applies to:

Siebel Workflow - Version: 7.7.2.6 SIA [18372] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

When more number of request are routed to the WFProc Batch Manager , then it might not able to process the request and logs error in the S_SRM_REQUEST.

Cause

WfProc Manager comp not able process more number of request coming and hence the error
SBL-SMI-00064: Internal: Multi-threaded server for component WfProcBatchMgr  in the S_SRM _REQUEST Table

Solution

Set the MaxMT and MinMT param to 2 for WFProc Batch Manager comp

References

NOTE:476018.1 - How to set Max Tasks and Max MT Server parameters for the Siebel Object Manager?
NOTE:477818.1 - How Synchronous and Asynchronous Server Requests Work, and How To Tune These Requests for Performance and Availability
NOTE:729037.1 - Asynchronous tasks get error out:

Applies to:

Siebel Workflow - Version: 7.7.2.6 SIA [18372] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

When more number of request are routed to the WFProc Batch Manager , then it might not able to process the request and logs error in the S_SRM_REQUEST.

Cause

WfProc Manager comp not able process more number of request coming and hence the error
SBL-SMI-00064: Internal: Multi-threaded server for component WfProcBatchMgr  in the S_SRM _REQUEST Table

Solution

Set the MaxMT and MinMT param to 2 for WFProc Batch Manager comp

References

NOTE:476018.1 - How to set Max Tasks and Max MT Server parameters for the Siebel Object Manager?
NOTE:477818.1 - How Synchronous and Asynchronous Server Requests Work, and How To Tune These Requests for Performance and Availability
NOTE:729037.1 - Asynchronous tasks get error out:

Applies to:

Siebel Workflow - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1241779801.

Symptoms

SBL-DAT-00171, SBL-SMI-00064   We are currently receiving the following error message in the Workflow Process Batch Manager logs,SBL-SMI-00064: Internal: Multi-threaded server for component (null) got a request for component (null). We have had this problem before and submitted SR #38-1178344271 to try to get it resolved. At that time the impact was much greater than it is today so we would like to catch this problem early before it begins to seriously impact our production environment. We are not aware of any harmful effects of these errors but suspect that something is not happening that should
   To resolve the previous issue we modified the number of MT servers and tasks. The current parameters for the Workflow Process Batch Manager and the Workflow Process Manager are:

Minumum MT Servers: 5
Maximum MT Servers: 10
Maximum Tasks: 200

   We usually have about 125 concurrent users all of whom run workflows at some point during the day. Do we have enough tasks to handle the load? What is the best way to determine if we have enough? Does something have to be done to turn on statistics for the component so we can monitor the process more closely? Thank you.

Bob Rabold

Cause

For the benefit of other user, customer observed the following error in the Workflow Process Batch Manager log file:

SBL-SMI-00064: Internal: Multi-threaded server for component (null) got a request for component (null).

Customer determined that there is a repeating component request that calls a Workflow Process Batch Manager component. This workflow process has a step that uses ‘“Synchronous Assignment Manager Requests”. There are also numerous AsgnSrvr log files in the server log directory.

Based on the above scenario, there error message is likely to be caused by not having sufficient task to handle the Assignment Manager request by the Workflow Process Batch Manager component.

Based on the information documented in Siebel Server Administration Guide v7.5.3 > Chapter 6: Siebel Server Infrastructure Administration > Administering Server Request Broker


The Server Request Processor (SRProc) and the Server Request Broker (SRBroker) are jointly responsible for the processing of both synchronous and asynchronous request.

“Synchronous Assignment Manager Requests” is a synchronous request and therefore, it involves SRProc and SRBroker.

Solution

The error was resolved after tuning the following components with the value set for parameters: Minumum MT Servers/ Maximum MT Servers/Maximum Tasks:

Server Request Broker    : 2/2/200
Server Request Processor    : 10/10/200
Workflow Process Manager    : 10/10/200

Keywords