Jobs remain in Queued Status for batch components like Workflow or Doc Server (Doc ID 1308717.1)

Last updated on JANUARY 17, 2017

Applies to:

Siebel CRM - Version 7.7.2.7 [18376] and later
Siebel 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:

- When attempting to execute a batch job through server manager commands, the following errors were displayed:.
     SBL-ADM-60070: Error reported on server 'server1' follows:
     SBL-SVR-01014: Internal: Could not send the HELLO message: (null)
     SBL-NET-01023: Peer disconnected
- The submitted job just stayed on 'Queued' status.
- The behavior also occured on GUI.


Another case:

- A Repeating Component Job (RCR) was submitted.
- The jobs were executed successfully and suddenly new jobs just stayed on 'Active' or 'Queued' status.
- The Siebel services were restarted and the pending jobs were executed successfully until the new jobs stayed again on 'Active' or 'Queued' status

 

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  127.0.0.1:63471 to 127.0.0.1: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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms