BPEL Exception : ORABPEL-05002

Error ORABPEL-05002 in domain log
Failed to handle dispatch message ... exception ORABPEL-05002Message handle error.An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage";the exception is: Transaction was rolled back: timed out;nested exception is: java.rmi.RemoteException:No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is: java.lang.Exception: No Exception - originate from:

The root cause of this problem is poor performance of the dehydration store database. Following are the possible ways to overcome such problem:
1.If you are using Oracle Lite as dehydration store, switch to use Oracle 9i or 10g.( Better use 10g above version 10.2.0.1)
2. Increase the maxConnection number of the BPELServerDataSource. OC4J has too few available connections to the dehydration database.Location: /j2ee/home/config/data-sources.xml
(NOTE: If you are using10.1.3.4, then you need not worry because it is already set as maximum by default)
3. Size of message is too big. Two ways to deal with this problem:
a. Increase the transaction timeoutLocation :/j2ee/home/config/server.xml
b. Decrease the auditLevel from BPELConsole. It will reduce the amount of data saved to the dehydration store.Location: BPEL Console -> Manage BPEL Domain -> Configurations tab.

I hope this will solve your problem