IP17 JMSReceiver Still Invokes The Workflow Process Even After A Timeout Has Occurred And There Are No Messages Picked Up From The JMS Queue
(Doc ID 2448082.1)
Last updated on JANUARY 29, 2021
Applies to:Siebel CRM - Version 17.5 [IP2017] and later
Information in this document applies to any platform.
On : 17.5 [IP2017] version, Siebel EAI
In IP17 version, when the JMSReceiver component task encounters a timeout (default 120 seconds) due to no messages in the JMS queue to pick up, it still invokes the dispatch workflow without a message, which leads to the workflow process to be executed - but without valid data and generates an error message. This goes on for all 4 child receiver threads.
When restarting the JMSReceiver again with same parameters and no message in the queue, it fails the same way so it goes into an infinite loop of invoking the workflow process without any valid data/message and fails.
The error in this particular scenario involves a UCM workflow process which fails with this error since there are no actual message picked up, so no actual values, etc. to run the workflow process on, which led to this error:
The JMSReceiver timed out after 120 seconds but it still invoked the dispatch workflow without a message which leads to the workflow process execution. This goes on for all 4 child receiver threads.
When restarting the JMSReceiver again with same parameters and no message in the queue, it fails the same way so it goes into an infinite loop.
Due to this issue, users cannot use the JMSReceiver correctly.
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