SOA 11g: Composite State not Updated after BPEL Recovery of Faulted Instance
Last updated on JUNE 01, 2016
Applies to:Oracle SOA Platform - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
The state of a failed SOA composite application instance is not updated after you successfully perform a recovery from the Recovery page of the BPEL service engine.
For example, assume you perform the following steps.
- Enable payload validation on the SOA Infrastructure Common Properties page in Oracle Enterprise Manager Fusion Middleware Control Console.
- Invoke an instance of a SOA composite application. If payload validation fails (for example, because required elements in the schema are missing), a failure occurs at the BPEL service component level during execution of an invoke activity.&
The instance is displayed as faulted in the Dashboard and Instances pages of the composite.
- Go to the Recovery page of the BPEL service engine and note that the same instance is pending recovery.
- Disable payload validation on the SOA Infrastructure Common Properties page.
- From the Recovery page of the BPEL service engine, select the instance and click Recover. This recovers the instance.
- View the completed instance in the flow trace. However, note that the instance state is not updated and is still shown as faulted, whereas the instance has actually recovered and completed successfully.
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