Payload Changes, from Recoverable Instances, are not Handled Correctly
(Doc ID 1300744.1)
Last updated on SEPTEMBER 03, 2019
Applies to:
Oracle SOA Suite - Version 11.1.1.3.0 to 11.1.1.4.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
- On SOA 11.1.1.3 modified payload information in the EM console from a recoverable instance does not take effect after the instance has been recovered.
- As a result, on recovery the value of an input variable remains the same and the process instance stops again with an error.
Changes
When recovering a BPEL component with one-way or two-way async invocation pattern and update the variable used for initial <receive> / <pick/onMessage> via EM console, this variable will keep it's original value when OneWayDeliveryPolicy=async.persist is configured.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |