Siebel SWSE Processes Running on IHS Never Finish and Cause Memory Leak
(Doc ID 2727286.1)
Last updated on NOVEMBER 09, 2020
Applies to:Siebel CRM - Version 18.104.22.168  to 16.19 [IP2016] [Release V8 to V16]
Information in this document applies to any platform.
IBM IHS web server memory leak caused by hanging threads waiting for Object Manager response
Below is the typical call stack obtained for the httpd process
Backend Siebel Server processes were reviewed, and not found as in hung state whatsoever.
No actual outstanding TCP connection could be associated with the hanging httpd threads in SISMsgQ::GetMsg.
IBM IHS web server spawns new workers, and old workers stay as outstanding processes consuming resources, ie RAM and CPU, with no activity.
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