Payload Changes, from Recoverable Instances, are not Handled Correctly
Last updated on NOVEMBER 03, 2016
Applies to:Oracle SOA Platform - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
- On SOA 22.214.171.124 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.
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.
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