Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
custom application (e.g. java application) that uses Siebel Business Object Interfaces of Siebel Object Manager component (e.g. accessed via Siebel Java Data Bean instance) performing logic below:
1. make connection to Siebel Object Manager and log in
2. creates instances of a Siebel Business Object and Business Components and Business Components of the Siebel Product Promotion Framework
3. for a given (by Id) Product Promotion, add and/or removing different products items in the product domain.
4. at the end release objects and log off to end Siebel Object Manager session
Siebel Object Manager server component processes crashes after execution of the above outlined logic for multiple promotions.
Checking crash files indicates memory exhausting for the Siebel Server component process (MT Server) - it was approaching 2 GB limit (highest memory space accessible to a 32-bit process).
It was noted that after completion of each run (Siebel Object Manager session - Siebel Component task) Siebel Component process (MT Server) consumed more and more more OS memory.
Component Tasks did not release the private memory cash of Siebel Promotion Objects after log off.
Same functionality (adding / removing items of a product domain in the product prompotion) executed interactively in Siebel Client (Siebel UI) did NOT show the issue: cash was released at the log off.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms