Siebel OM Components Crashing with High Process Memory Consumption Post Deploying Code Changes
(Doc ID 2992002.1)
Last updated on DECEMBER 08, 2023
Applies to:
Siebel CRM - Version 19.7 and laterInformation in this document applies to any platform.
Symptoms
Memory leak crashes reported for htimObjMgr_enu after importing new metadata changes in repository & deploying code changes. Frequent OM crashes which process memory reached around 3.8 to 4 GB which caused production system unstable.
Line 65: ServerLog ProcessCreate 1 00000003652f81f2:0 2023-10-18 00:17:16 Created server process (OS pid = 33999 ) for htimObjMgr_enu
Line 208: ServerLog ProcessExit 1 00000004652f81f2:0 2023-10-18 10:03:41 htimObjMgr_enu 33999 SBL-OSD-02006 Process 33999 exited with error - Process exited because it received signal SIGABRT.
Line 208: ServerLog ProcessExit 1 00000004652f81f2:0 2023-10-18 10:03:41 htimObjMgr_enu 33999 SBL-OSD-02006 Process 33999 exited with error - Process exited because it received signal SIGABRT.
The issue can be reproduced at will with the following steps:
1. Import new repository changes from Development to Production environment
2. Restart Siebel Services
3. Allow users to connect in Siebel Application Object Manager
4. After few hours the Siebel processes are starting to exit with error and users are experiencing server busy error in between navigation
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 |