Upon a Transaction Rollback Exception, ORABPEL-05007, there is no Fault Saved in WI_FAULT Table
(Doc ID 1495795.1)
Last updated on AUGUST 07, 2018
Applies to:Oracle(R) BPEL Process Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Business Flow : BPEL -> Spring -> EJB
In a BPEL processe we invoke a Spring Component which invokes a remote EJB3 component. All this invocation stack is made transactional using JTA. When an Exception occurs in one of the remote EJB3 3 methods, this Exception is catch by Spring component , but is not propagated to BPEL. Actually it seems that BPEL catches the fault but is not able to log it because it tries ti use an existing transaction to persist that fault to the RDBMS. But transaction has been already rolled back because of Exception in EJB method.
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