Thursday, October 15, 2020

12c SOA Synchronous BPEL process with a wait activity fails with a timeout

The Wait activity works well with an asynchronous BPEL process but not with a synchronous BPEL process where a transaction is required. The Wait activity involves a dehydration. Dehydration will persist the process and continue the process in a new thread. When the BPEL process is transaction required, the persist will not be complete until the BPEL process completes and transaction commits.

Synchronous BPEL process with a wait activity fails with a timeout

One of the solutions is possible:

Remove the following line from the synchronous BPEL process component:

required

OR

Change bpel.config.transaction to “requiredNew”

requiredNew

No comments:

Post a Comment

Featured Post

OIC - Sending JSON Data as Email Body Content via Twilio SendGrid API in OIC

Use Case Description: When integrating Oracle Integration Cloud (OIC) with Twilio SendGrid API to send emails, JSON data intended for the em...