How to catch BPELFault after exception "JTA transaction is not present or the transaction is not in active state"
(Doc ID 1400936.1)
Last updated on MARCH 20, 2019
Applies to:
Oracle(R) BPEL Process Manager 10g - Version 10.1.3.5.0 and laterInformation in this document applies to any platform.
***Checked for relevance on 01-July-2014***
Goal
BPEL process collects information by interacting with several other BPEL processes. One of the called BPEL process was intermittently runs into error -
"There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "ID". The reason is The execution of this instance "ID" for process "<name>" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your admini "
Once the exception was thrown, the called BPEL process does not stay in the same transaction and hence the error can not be propagated. Is there a way to capture the exception and resubmit the BPEL process?
Solution
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
| Goal |
| Solution |
| References |