Siebel Find Cause Leak Message (Doc ID 2253504.1)

Last updated on APRIL 26, 2017

Applies to:

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

Symptoms

On :  16.8 [IP2016] version, System Admin

ACTUAL BEHAVIOR  
---------------
In standard Siebel setup with IP 2016.6 on Linux 6.5 (Exalogic VM), the following messages are found on OM log file at the end of the task when the user does a logoff or the task times out:

Line 46545: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Service leak: Invoke Search
Line 46546: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Service leak: Search Manager Service
Line 46547: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Service leak: Search External Service
Line 46549: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Service leak: Search Execution Service
Line 46577: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Object leak: Search BO
Line 46578: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Object leak: Calendar
Line 46579: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:55 Business Object leak: Account
Line 46691: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:57 Business Service leak: Invoke Search
Line 46692: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:57 Business Service leak: Search Manager Service
Line 46693: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:57 Business Service leak: Search External Service
Line 46695: ObjMgrSessionLog Debug 5 0000010758967aa1:0 2017-02-14 12:06:57 Business Service leak: Search Execution Service

EXPECTED BEHAVIOR
-----------------------
The messages are expected to help as memory leak indicators, but there are messages being written for standard Siebel objects

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Log-in
2) Open Advanced Find
3) Select "Account" category
4) Enter a search
5) Execute the search via button
6) Log-out


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, it is not possible to rely on the leak messages in the OM logs as indication of memory leak issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms