My Oracle Support Banner

Cube delivery, Cannot deserialize DOM element. failure to deserialize the document xxxxxxx from binary format during dehydration. (Doc ID 2895588.1)

Last updated on JANUARY 08, 2024

Applies to:

SOA Suite Cloud Service - Version 12.2.1.3 to 12.2.1.4
Information in this document applies to any platform.

Goal

 
SOACS - Integration errors out with no error message - The reason was .  

We're facing an strange error from one integration, and it asks to contact Oracle support, I'll upload the .out logfile.

the exception reported is: java.io.IOException: ORABPEL-09222

Cannot deserialize DOM element.
failure to deserialize the document  from binary format during dehydration.
The exception reported was: XML Document creation failed.
error while creating the XML document.
The reason was XML Document creation failed.
error while creating the XML document.
The reason was .
Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

 

<Aug 26, 2022 7:38:32,336 PM UTC> <Error> <oracle.soa.bpel.system> <BEA-000000> < [cube delivery, Cannot deserialize DOM element.
failure to deserialize the document xxxxxxxxxxxxxxxxxxxxxx from binary format during dehydration.
The exception reported was:  .
Contact Oracle Support Services.  Provide the error message and the exception trace in the log files (with logging level set to debug mode)
]
 ** InvokeMessageGuid: xxxxxxxxxxxxx
 ** ComponentDN: default/xxxxxxxxxxxxxxxxx!1.0/xxxxxxxxxxxxxTransformBpelProcess
 ** Properties for component xxxxxxxxxxxxxTransformBpelProcess:
   ** bpel.config.transaction: notSupported
   ** bpel.config.oneWayDeliveryPolicy: async.persist
 ** MaxThreadsConstraints: 145
 ** Total dispatcher messages scheduled for processing: 0
 ** Total number of threads processing dispatcher messages: 5
 ** Max Heap size: 8552710144
 ** Free Heap size: 4276422056
ORABPEL-09222

Cannot deserialize DOM element.
failure to deserialize the document xxxxxxxxxxxxxxxxxxxxx from binary format during dehydration.
The exception reported was:  .
Contact Oracle Support Services.  Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.