Last updated on APRIL 26, 2011
Applies to:Oracle ESB - Version: 10.1.3.3.1 to 10.1.3.4 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 26-Apr-2011***
ESB 10.1.3.3.1 - When using the ESB Client API to resubmit failed ESB instances, you may see an error like the following:
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
"270067-BpInv0-BpSeq0.3-4". The reason is The execution of this instance
"270067-BpInv0-BpSeq0.3-4" for process "xxbcfEsbErrorRetryBpel" 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 administrator regarding this error. " Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.less
Yet you can successfully resubmit the same instance from the ESB console.
ESB 10.1.3.4 - When using the ESB Client API to resubmit failed ESB instances, the resubmission succeeds without errors, but the ESB instances remain in an error state. Yet, again, the instances can be successfully resubmitted from the ESB console.
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