SOA 11g - BPEL OnMessage Processing is not Thread-safe
Last updated on JANUARY 26, 2018
Applies to:Oracle SOA Platform - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11gR1]
Information in this document applies to any platform.
When two or more messages come to the same BPEL process on the onMessage branch at the same time, they produce wrong outputs: one message gets processed end to end (but with wrong values, as it takes values from another parallel message), and the others are timing out.
The expected behaviour is that concurrent callback messages should not interfere with each other, and invocations should finish correctly and with correct values.
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