ORABPEL-05002 when trying to recover a Business Fault

(Doc ID 1407528.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.4.0 and later
Information in this document applies to any platform.
***Checked for relevance on 23-July-2013***

Symptoms

You may be facing this issue if you are testing a composite application that is throwing (by design) multiple recoverable business faults but when trying to recover from them, the process fails again, this time with time-out faults.

Also, in the log files you should notice a similar error stack:


Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage";
the reported exception is: Block cannot handle exception.
failure of the block "BpPrc0" to handle a business exception for the instance
"70014"; exception reported is: faultName:
{{http://xmlns.oracle.com/BPELSamples/FaultManag/BPELProcess1}SomeBusinessFault}
messageType:
{{http://xmlns.oracle.com/BPELSamples/FaultManag/BPELProcess1}BPELProcess1FaultMessage}
parts: {{
payload=<someFault
xmlns="http://<someURLhere>/schema.xsd"><affaire>13</affaire><action>ERROR</action><workflow>TOTO</workflow></someFault>}

This error contained the exceptions thrown by the underlying routing system.
Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002

Message handle error.
error while attempting to process the message
"com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage";
the reported exception is: Block cannot handle exception.
failure of the block "BpPrc0" to handle a business exception for the instance
"70014"; exception reported is: faultName:
{{http://xmlns.oracle.com/BPELSamples/FaultManag/BPELProcess1}SomeBusinessFault}
messageType:
{{http://xmlns.oracle.com/BPELSamples/FaultManag/BPELProcess1}BPELProcess1FaultMessage}
parts: {{
payload=<someFault
 xmlns="http://<someURLhere>/schema.xsd"><affaire>13</affaire><action>ERROR</action><workflow>TOTO</workflow></someFault>}

This error contained the exceptions thrown by the underlying routing system.
Contact Oracle Support Services. Provide the error message, the composite
source and the exception trace in the log files (with logging level set to
debug mode).

This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:207)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)



You may also be facing the same issue in a synchronous BPEL process that has a mid-process Receive/onMessage/Wait activity. If some fault is thrown after that activity and caller thread times-out, you could see the same error in the log files.

Cause

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