Please solve "com.collaxa.cube.engine.EngineException"

Question

iam using Oracle Soa11g
Weblogic 10.3
i use one bpel,mediator,File adapter.Test service is successful but in the instance it shows recover needed
<exception class="com.collaxa.cube.engine.EngineException">
Global retry rollback fault thrown. The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault. This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval. There is no action recommended.
<stack>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#330</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1056</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#583</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#130</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#158</f>
<f>com.collaxa.cube.engine.CubeEngine._performActivity#2463</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2334</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1115</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#73</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#220</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#328</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4350</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4281</f>
<f>com.collaxa.cube.engine.CubeEngine.createAndInvoke#679</f>
<f>com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke#654</f>
<f>...</f>
</stack>
</exception>
</fault>
</messages>
Nov 3, 2012 11:01:01 AM The transaction was rolled back. The work performed for bpel instance "20004" was rolled back, but the audit trail has been saved for this instance.If this is a sync request, please resubmit the request from the client. If it is an async request, please recover from the recovery console by resubmitting the invoke message.
Fetching Data...
The transaction was rolled back. The work performed for bpel instance "20004" was rolled back, but the audit trail has been saved for this instance.If this is a sync request, please resubmit the request from the client. If it is an async request, please recover from the recovery console by resubmitting the invoke message.
OK
OKCancel

Answer 1

Seems BPEL invoke is timing out. Check why BPEL invoke timed out and that should solve your problem. The instance audit trail or the server diagnostic log may help you in finding the exact problem.
Regards,
Anuj