Async MDN Send Error Producing An Invalid correlationID (Doc ID 2204071.1)

Last updated on NOVEMBER 15, 2016

Applies to:

Oracle SOA Suite - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3.0.0 version, B2B Engine

Async MDN send error producing an invalid XML document where the correlationID is incorrectly packaged.

When an Async MDN fails to send, that exception being written the the exception queue for another composite to pickup that message. The composite fails with the following error message.


ERROR
-----------------------

DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Please make sure that the xml data is valid.

<1410449450773.28606326@ddcaxpcimgw02_te> 819B81D2148658D9E3900000269681B8 B2B-50079 2 <parameter name="b2b.messageId" value="819B81D2148658D9E3900000269681B8"/> <parameter name="b2b.replyToMessageId" value="<1410449450773.28606326@ddcaxpcimgw02_te>"/> <parameter name="b2b.documentTypeName" value="Acknowledgement"/> <parameter name="b2b.messageType" value="3"/> <parameter name="b2b.fromTradingPartnerId" value="Intermountain"/> <parameter name="b2b.fromTradingPartnerIdType" value="Name"/> <parameter name="b2b.toTradingPartnerId" value="McKPharmaProd"/> <parameter name="b2b.toTradingPartnerIdType" value="AS2 Identifier"/>


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot subscribe to exception messages and get notified.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms