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


תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא