SOA 11g: "weblogic.transaction.internal.TimedOutException" BPEL Instances Stuck on Running State after Transaction Timeout Exception
(Doc ID 1518358.1)
Last updated on SEPTEMBER 03, 2019
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1 to 11g]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, BPEL Service Engine
When a transaction timeout occurs on an activity(assign/java embedding etc) after a dehydration point in BPEL process, the transaction is getting rolled back to the last dehydration point and the BPEL process is stuck in the Running state forever.
SOA Should provide a way to recover the instances which got stuck in Running state
The issue can be reproduced at will with the following steps:
1. Create a BPEL with dehydration point (for eg. Human task with response) and add an assign activity after the receive node and make the assign activity run above transaction timeout.
2. Notice the transaction gets timed out and the control will be returned to the last dehydration point and BPEL will get stuck in running state.
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