JMSReceiver Fails Executing a Workflow Process That Calls Server Requests on the Second Time
(Doc ID 503645.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel System Software - Version 22.214.171.124 SIA  and later
Siebel CRM - Version 7.8.2 SIA  and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 126.96.36.199  Fin Svcs
Database: IBM DB2 8.1 FixPack 8
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
This document was previously published as Siebel SR 38-3106271535.
""""Checked for relevance on 05-JAN-2011""""
*** Checked for relevancy 31-Dec-2012 ***
The customer created a workflow called ‘EAI Inbound Postman DirectDB’ that was executed by the JMSReceiver when a message was put on a JMS queue. The workflow included a business service step called ‘Send Async Job (DirectDB) ZZZZZ' that invoked the SubmitRequest method on the Server Requests business service with Mode equal to DirectDb to invoke a Workflow Process Manager task.
When the customer started a JMSReceiver task and put a message on the queue, the message was picked up and the workflow was executed and completed correctly. When the customer put a second message on the queue, the message was picked up, the workflow was executed but the following error occurred when the step that invoked Server Requests was executed:
This operation is not allowed when there are no records displayed.
Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)”
The task’s log showed that immediately before the error occurred it tried to delete the server request:
“SRMBusSvc:DoInvokeMethod(): Request Record added for WfProcMgr with id 1-ABJ5
2006-08-11 10:09:40 INSERT/UPDATE statement with ID: Unknown
DELETE FROM SIEBELDBA.S_SRM_REQUEST
WHERE ROW_ID = ?
Bind variable 1: 1-ABJ5”
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