CSM Component Hanging Up With Max Tasks Reached
(Doc ID 1937088.1)
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 126.96.36.199  and later
Information in this document applies to any platform.
On : 188.8.131.52  version, CTI
The customer would like to know what could have led one of their ComSessionMgr-component yesterday to reach max tasks.
The workload is evenly load balanced among 10 interactive Siebel Servers. The CSM component hung, after this point all tasks were stuck in a “Running” state. It was noticed that the SISPROCID was equal to “18”, an even value. When the issue occured the the Component ID in the CSM log file changed from 18 to 19:
The following error was also recorded in the CSM log file:
GenericLog GenericError 1 017ef09b541e0008:0 2014-09-25 16:59:26 (sisobj.cpp (1288) err=1310742 sys=0) SBL-SVR-00022: Die Funktion ist nicht implementiert
Translated into English:
GenericLog GenericError 1 000001f14f3d13d8:0 2012-02-17 05:48:18 (sisobj.cpp (1288) err=1310742 sys=0) SBL-SVR-00022: The function has not been implemented
The customer also took a procstack of the hung process which look as follows:
0xd04f1564 _event_sleep(??, ??, ??, ??, ??, ??) + 0x584
0xd04f2004 _event_wait(??, ??) + 0x2c4
0xd0500480 _cond_wait_local(??, ??, ??) + 0x500
0xd0500a50 _cond_wait(??, ??, ??) + 0xb0
0xd0501728 pthread_cond_wait(??, ??) + 0x1a8
0xd05b4500 osaWaitEvent_AIX53(void*,int)(??, ??, ??, ??, ??) + 0xd0
0xd05b3dc0 osaWaitEvent_AIX53(void*,int)(??, ??) + 0x30
0xd0e79abc osaWaitEvent(void*,int)(??, ??) + 0xc
0x1002f558 _smiWorkQueue::GetNextWorkItem(_thrdQItem*,_queueItem*&)(??, ??, ??) + 0x638
0x1002c23c _smiWorkQueue::WorkerTask(void*)(??) + 0x31c
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.|