Jobs remain in Queued Status for batch components like Workflow or Doc Server
(Doc ID 1308717.1)
Last updated on OCTOBER 30, 2023
Applies to:
Siebel CRM - Version 7.7.2.7 [18376] and laterSiebel System Software - Version 7.7.2.7 [18376] and later
Information in this document applies to any platform.
Symptoms
It was observed that jobs submitted by srvrmgr or SRProc were not successfully run or remained in status 'Queued' or Active' for no obvious reason.
It was verified that the SRBroker, the SRproc and the target component like for example Wfprocmgr, Doc Server or FSMsrvr were online.
Example of the error scenario:
In the SRBroker log the following error can be found:
SisnTcpIp SisnSockDetail 4 0000046f55c8a128:0 2015-08-10 16:55:18 26192: [TCPIP-client] socket() opened descriptor = 3760 from <IP address loopback adapter>:63471 to <IP address loopback adapter>:49153
SisnTcpIp SisnSockDetail 4 0000046f55c8a128:0 2015-08-10 16:55:18 26192: [TCPIP-client] Send() descriptor = 3760
SisnTcpIp SisnSockDetail 4 0000046f55c8a128:0 2015-08-10 16:55:18 26192: [TCPIP-client] Read() descriptor = 3760
GenericLog GenericError 1 0000046f55c8a128:0 2015-08-10 16:55:18 (srbthrd.cpp (2718) err=1180671 sys=0) SBL-NET-01023: Peer disconnected
GenericLog GenericError 1 0000046f55c8a128:0 2015-08-10 16:55:18 (srbthrd.cpp (2718) err=3735593 sys=0) SBL-SRB-00041: Could not send a SISNAPI hello message after connecting to the component.
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 |