Last updated on JULY 17, 2014
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
In an asynchronous BPEL process there are 3 correlation sets defined along with their respective correlation properties.
Some of them are being instantiated on the very first "Receive" activity (name: Receive_Input). BPEL flow executes normally up the point when it reaches a "Pick" activity(name: Pick1) that the first correlation set is being utilized (and it has always been previously instantiated).
This "Pick" activity will hydrate the execution and it will be resumed as soon as a synchronous invocation will be received.
At that point, there is a random behavior occurring:
a) Either the pick activity will execute fine, meaning it will wait for the synchronous invocation to occur, and the process will continue normally.
b) An exception will be raised. The exception shown is:
*Note: The exception will occur almost instantly as the flow arrives at the pick action. Also, in the case described above there are no parallel flows being executed.
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