Workflow Jobs Stays in Active Status & Not Moving to Completed in Production
(Doc ID 2719147.1)
Last updated on OCTOBER 12, 2020
Applies to:Siebel CRM - Version 19.9 and later
Information in this document applies to any platform.
All of sudden workflow jobs stuck in Active/Queued status in Production. There are 10 Siebel servers dedicated for Siebel workflow component. The jobs are not being distributed evenly across the siebel workflow servers. Issue reported with srvr1, if this server is restarted, load is moving to other servers.
If job is resubmitted, job is successful.
During this SRBroker log reported with error:
SisnTcpIp SisnSockError 1 0000004c5f651546:0 2020-09-20 19:04:05 124: [TCPIP-client] recv() failed for sd=-1 (err=9 | Bad file number)
SisnapiLayerLog Error 1 0000004c5f651546:0 2020-09-20 19:04:05 124: [SISNAPI] Async Thread: connection (0x26ff888), error (1180852) while reading message
GenericLog GenericError 1 0000004c5f651546:0 2020-09-20 19:04:05 (srbclbck.cpp (759) err=1180852 sys=0) SBL-NET-01204: Internal: recv() failed: (null)
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