My Oracle Support Banner

Logoff Crashes and Workflow Process Manager BS Leak under Dispatch Board while DragnDrop of Gantt chart (Doc ID 2338318.1)

Last updated on JULY 07, 2020

Applies to:

Siebel CRM - Version 16.5 [IP2016] and later
Information in this document applies to any platform.

Symptoms

Siebel application(eChannel) object manager is crashing in production which are logff crashes. After analyzing, we understand that there BS leaks and steps to reproduce the same as:

Steps:

--------

Login to application and follow below steps

1. Sitemap > Dispatch Board > Unscheduled activities list
2. Select Service Region
3. drag and drop an unassigned activity on the gantt chart
4. Go to Home page
5. Log out

In OM log, could see BS & BO leaks

ObjMgrSessionLog Debug 5 000000025a0d21d2:0 2017-11-17 11:43:50 Business Object leak: Search BO

ObjMgrSessionLog Debug 5 000000025a0d21d2:0 2017-11-17 11:43:50 Business Object leak: Calendar
ObjMgrSessionLog Debug 5 000000025a0d21d2:0 2017-11-17 11:43:50 Business Object leak: Process/Task Analytics
ObjMgrSessionLog Debug 5 000000025a0d21d2:0 2017-11-17 11:43:50 Business Object leak: Workflow InstanceEx BO
ObjMgrSessionLog Debug 5 000000025a0d21d2:0 2017-11-17 11:43:50 Business Object leak: Front Office Workflow
ObjMgrBusCompLog Delete 4 000000025a0d21d2:0 2017-11-17 11:43:50 BusComp "Process/Task Analytics Timestamp" at 2a052350 was deleted
ObjMgrBusCompLog Delete 4 000000025a0d21d2:0 2017-11-17 11:43:50 BusComp "Process/Task Analytics Metric" at 2a04dbf0 was deleted
ObjMgrBusCompLog Delete 4 000000025a0d21d2:0 2017-11-17 11:43:50 BusComp "Process/Task Analytics Flow Info" at 2a065530 was deleted
ObjMgrBusCompLog Delete 4 000000025a0d21d2:0 2017-11-17 11:43:50 BusComp "Workflow InstanceEx" at 29f87230 was deleted
ObjMgrBusCompLog Delete 4 000000025a0d21d2:0 2017-11-17 11:43:50 BusComp "Workflow Process Deployment" at 2a041f10 was deleted

Some times, OM will also crash especially in production environment with these leaks and below callstack

 

--- called from signal handler with signal 11 (SIGSEGV) --- 
f907bb10 void CSSBusObj::Release() (22dbc210, a, c82ad1d4, f91f8414, ffffffff, 10800) + 30 
e20da034 __SLIP.DELETER__G (29f63dd8, 1, feb9d0cc, e21ecac8, 2b7c, e20da020) + 14 
e1ef775c CSSWfEngine::~CSSWfEngine() (20120338, 2012055c, 2800, 2cc4, 2c00, 20120558) + 9dc 
e1f182e4 __SLIP.DELETER__O (20120338, 1, 20120414, c82ad334, 0, 0) + 4 
f8fdba98 void CSSService::Release() (e1f182e0, 201203dc, 114e2c14, 0, 20120430, f91f8414) + 178 
f8faabc8 void CSSModel::CleanupServices(const bool,const CCFArray*,CCFArray<ccfelemptr >*,const bool) (1dd22260, 0, 0, 0, 1dd22b00, f91f8414) + 248 
f8fc1bc8 void CSSModel::Release() (1dd22260, 0, f887c028, f91f8414, 39c00, 39c00) + 188 
f96062f8 int CSSSIOMSession::Logoff() (200a3908, fdc60754, c82adc28, f92004cc, 140000, 0) + 1f8 
f978ece0 unsigned CSSClient::HandleOMLogoff(CSSClientReq*) (12dddd00, c82ade78, 0, 0, 0, 1c74cac4) + 20 
f978b364 unsigned CSSClient::HandleRequest(CSSClientReq*) (12dddd00, c82ade78, 6000, f97aeee0, f97b0504, fdc68208) + a4 
f97874a8 int SOMMTServer::SessionHandleMsg(smiSisReq*) (dcaec8, 28171dc8, ff0c47e0, f97aeee0, c82ade78, feb6a64c) + 208 
0021b504 int smiMainThread::CompSessionHandleMsg(smiSisReq*) (735b60, 28171dc8, 4, 2a67ac, 205c2668, 28171ddc) + 164 
00248efc int _smiMessageQ::ProcessMessage(_smiMsgQItem*,long,int) (e09620, 19afe540, 22e85c80, fdc69248, 2a67ac, 19dadf20) + 105c 
00246b9c int _smiMessageQ::ProcessRequest(void*,void*,void*&) (287fa370, 19afe540, 67, 0, 19dadf20, c82af494) + 21c 
00236b10 int _smiWorkQueue::WorkerTask(void*) (0, e09bf0, 1e175868, 287fa370, 2a67ac, feb8e8cc) + 370 
00221208 int SmiThrdEntryFunc(void*) (1a4, 0, 200, 2367a0, 208f5c30, ae259a0) + 448 
fe75f9e8 unsigned OSDWslThreadStart(void*) (27b3a9b0, 2074cd10, 220dc0, 1ec, 2000, 0) + a8 
fe39ccfc unsigned _AfxThreadEntry(void*) (c8f6dbec, 4000, 11648, c82afe10, fe480290, 1ebb3ac8) + f0 
fcdd1a8c void MwThread(void*) (1, 1ff0d430, 1ff0d430, 0, fcec9ca4, 0) + 29c 
fc6faf70 _lwp_start (0, 0, 0, 0, 0, 0) 


 SBL-OSD-00001: Internal: Function call timed out (0)
 SBL-OSD-02004 Process 28937 exited with error - Process exited because of an illegal instruction (SIGILL).

SBL-OSD-00001 Process 5196 exited with error - Internal: Function call timed out (%sysError)
SRBroker 28935 SBL-OSD-02011 Process 28935 exited with error - Process exited because of a segment violation (SIGSEGV)

Issue is reproducible with vanilla 16 & IP17 as well .

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.