My Oracle Support Banner

SRBroker Crashes Due To Process Memory Size Reaching OS Limits In Few Minutes (Doc ID 2671583.1)

Last updated on MAY 18, 2020

Applies to:

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

Symptoms

SRBroker is crashing when a significant load of synchronous requests are received by integrations through inbound EAI requests for Order creation.
SRBroker memory size (VSZ) is around 200-400 MB and is pretty stable, but at times when this high load is received SRBroker memory size (VSZ) jumps from 200-400 MB to 2 GB in a couple of minutes.
When the OS limits for 32-bit processes is reached SRBroker process crashes, which leads to a severe impact on the Enterprise stability.

The SRBroker logs with events set to 4 contains a large number of counts related to "PSP Transform L1" cache events.
The first column represents the number of events associated with a client process id (last column). In this particular case the PID 27000954 relates to the SRBroker process itself.

 

 

 

Changes

Significant increase on the load in a very short of time 

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


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