ORABPEL-09222 Document not found in datasource

Question

We are running BPEL 10.1.3.3.
We run seperate App and Database Servers. During a test, the network was disconnected between the App and Database Server, which resulted in a message being placed on the Invoke Manual Recovery Queue.
When I try and recovery this message, get heaps of Java Stack Trace in the domain.log and the message cannot be recovered.
Example of the stack trace below. Has anyone else seen this, or know the cause?
Pete
<2008-01-17 11:49:24,257> <ERROR> <default.collaxa.cube.engine.data> <BaseDeliveryPersistenceAdaptor::loadInvokeMetaData>
ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60. The exception reported is Document not found in datasource.
The process domain was unable to fetch the bytes for the business document "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" from the datasource.
Please check that the business document identifier "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" refers to a valid entry in the document table; this row may have been manually removed from the table.
     at com.collaxa.cube.xml.dom.SDOMHelper.loadCompressedNormalDocuments(SDOMHelper.java:384)
     at com.collaxa.cube.xml.dom.SDOMHelper.loadDocuments(SDOMHelper.java:153)
<2008-01-17 11:49:24,273> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": [com.collaxa.cube.engine.data.DataStreamException: Cannot decode properties.
The process domain was unable to decode the properties for message guid 10, which are stored in column Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60.  The exception reported is Document not found in datasource.
The process domain was unable to fetch the bytes for the business document "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" from the datasource.
Please check that the business document identifier "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" refers to a valid entry in the document table; this row may have been manually removed from the table.
; the exception reported is: {2}
sql statement: SELECT conv_id, message_guid, domain_ref, process_id, revision_tag, operation_name, receive_date, state, priority, properties, master_conv_id, headers_ref_id FROM invoke_message WHERE message_guid = ?
ORABPEL-04025
Cannot decode properties.
The process domain was unable to decode the properties for message guid 10, which are stored in column Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60. The exception reported is Document not found in datasource.
The process domain was unable to fetch the bytes for the business document "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" from the datasource.
Please check that the business document identifier "ec04eb2f0c9f4507:6adb5099:11781f7931e:-7f60" refers to a valid entry in the document table; this row may have been manually removed from the table.
; the exception reported is: {2}
sql statement: SELECT conv_id, message_guid, domain_ref, process_id, revision_tag, operation_name, receive_date, state, priority, properties, master_conv_id, headers_ref_id FROM invoke_message WHERE message_guid = ?
     at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.loadInvokeMetaData(BaseDeliveryPersistenceAdaptor.java:2029)
     at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.__loadInvoke(BaseDeliveryPersistenceAdaptor.java:1932)
...

Answer 1

looks like during recovery it is not able to fetch the message header elements for the invoke-message. is it possible to provide a test case with instructions to reproduce this problem? also can you please file a SR and upload all your supported files (test case, input xml, the current log files which has the exception trace).