SCBroker Component Termination/Crash Leads to Siebel Application Object Manager Crashes - Gateway Registry read failed
(Doc ID 2862250.1)
Last updated on JANUARY 26, 2024
Applies to:
Siebel CRM - Version 22.1 to 22.3 [Release V17]Information in this document applies to any platform.
Symptoms
SCBroker Component is crashing and the following callstack information is found:
Called from:
/siebel/ses/siebsrvr/lib/libsslcosd.so(+0x71c5)[0xf79d21c5]
/siebel/ses/siebsrvr/lib/libsslcosd.so(+0x79be)[0xf79d29be]
[0xf7f82330]
[0xf7f82319]
/usr/lib/libc.so.6(gsignal+0x47)[0xf73231c7]
/usr/lib/libc.so.6(abort+0x143)[0xf7324a03]
/usr/lib/libc.so.6(+0x70f75)[0xf7364f75]
/usr/lib/libc.so.6(+0x79a0d)[0xf736da0d]
/siebel/ses/siebsrvr/lib/libsslcgtwyregistry.so(CSSGatewayRegistry::Read(SSstring const&, SSstring&)+0x9a)[0xf7050aca]
/siebel/ses/siebsrvr/lib/libsssrvcdisc.so(SD_UpdateSvcPIDState_internal(SD_Service_Info_tag*, int, char16_t const*)+0x499)[0xf75fb879]
/siebel/ses/siebsrvr/lib/libsssrvcdisc.so(SD_UpdateSvcPIDState(SD_Service_Info_tag*, int, char16_t const*)+0x2b)[0xf75fee4b]
/siebel/ses/siebsrvr/lib/libsssacbrkr.so(SCBroker::SD_NotifyGateway(long,int, int)+0x539)[0xf5d08d59]
/siebel/ses/siebsrvr/lib/libsssacbrkr.so(ScbRREnhancedLBStrategy::SelectInstance(ScbProcessEntry&)+0x2eb)[0xf5d0cd2b]
/siebel/ses/siebsrvr/lib/libsssacbrkr.so(SCBroker::TransferToComponent(long,unsigned int)+0x26c)[0xf5d0980c]
/siebel/ses/siebsrvr/lib/libsssacbrkr.so(SCBroker::DispatchConnection(CSSSISCommSrvr*)+0x9c5)[0xf5d0b405]
/siebel/ses/siebsrvr/lib/libsssacbrkr.so(SCBroker::Start()+0x1d8)[0xf5d0b768]
In the corresponding SCBroker log file, located under siebsrvr/enterprises/<enterprise_name>/<siebel_server_name>/log directory, the following error can be observed:
It is necessary to restart the Siebel Server to recover from this behavior.
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 |
| Cause |
| Solution |
| References |