Please Explain ORABPEL-05002 for this process

Question

I have a very simple BPEL process which pulls messages off the Oracle AQ and sends them on to a BPEL process correlated to the received string data.
Step 1. An async partner link on the Oracle AQ to recieve a message
Step 2. It waits a minute
Step 3. Moves the single string (6 character #) from the message to and outbound service message
Step 4. Send the async outbound message to a BPEL process
Step 5. Terminate instance
I don't see how I'm getting a timeout exception (ORABPEL-05002) on the inbound message, unless BPEL holds the inbound transaction until the entire process is finished.
A. Does BPEL hold up closing the message transaction until the entire process has finished?
B. Can anyone suggest why the original developer added the one minute wait just after receiving the message?

Answer 1

These are the possible cause to the problem and their solutions:
Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
OC4J has too few available connections to the dehydration database. Increase the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
Size of message is too big Two ways to deal with this problem:
Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation)
Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
Cheers
Anirudh Pucha