How to troubleshoot Siebel SRBroker hangs
(Doc ID 1517299.1)
Last updated on NOVEMBER 15, 2019
Applies to:Siebel CRM - Version 7.7.2 SIA  and later
Information in this document applies to any platform.
This document is intended to assist in identifying and resolving hangs of the Siebel component SRBroker.
SRBroker is one of the most critical components in a Siebel enterprise and hangs of this component can have a wide effect and cause severe disruption for the entire enterprise.
Since each SRBroker is talking to other SRBrokers in the enterprise, a hang of one SRBroker can be propagated to other nodes in the enterprise and at some point, all server in the enterprise are affected and the entire enterprise needs to be bounced.
It can happen that the SRBroker process is in a state of a hang, although it shows up in srvrmgr as running.
The symptoms of a hanging SRBroker are manifold. Some of the most common effects are:
- File attachments can not be accessed anymore
- CTI requests not working
- Asyncroneous jobs run through SRProc are not processed
- WfProcMgr is not running any workflows
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