How to Use the Same Operation in Entry and Mid process Receive Activities
(Doc ID 2379166.1)
Last updated on MARCH 27, 2018
Applies to:Oracle SOA Suite - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Fabric
Receive activity from JMS adapter of Completed BPEL instance still somehow connected to JMS adapter
A singleton BPEL has two Receive activities connected to the same JMS queue (thru JMS adapter).
The beginning Receive (Receive0) initiates the instance, and the mid-process Receive (Receive1) does NOT create initiate instance.
Thru the correlation set mechanism, first JMS message initiates the BPEL instance, and subsequent JMS messages are consumed by Receive1 in a loop (thus achieving BPEL singleton). After the Receive1 loop finishes and the BPEL instance completes, if I put another JMS message into queue, it is supposed to be received by Receive0 and initiates another BPEL instance, BUT that did not happen.
After deleting the previously completed BPEL instance manually from EM console (or redeployed the SOA composite) for that to happen (queue message consumed by Receive0 initiating new BPEL instance).
The behavior is like Receive1 in the completed BPEL instance still connects with the queue and prevents Receive0 from consuming JMS message. After the BPEL instance is completed, I put another message into queue, it is consumed (not in queue), but NOT by Receive0.
For the mid process receive to work as expected as in
9.3.2 How to Use the Same Operation in Entry and Mid process Receive Activities
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!