B2B 11g - AS2 Data Stuck In Processing Status And Not Sending MDNs
(Doc ID 1599713.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle B2B 10g (Business to Business) - Version 10.1.2.0.0 and laterInformation in this document applies to any platform.
Symptoms
A trading partner sent an AS2 message which failed with B2B-50547 error and sent a rejected MDN. However, the initial wire message stayed in processing state and every resend of the message failed with a B2B-50081 error, but no MDN is sent back.
In SOA server diagnostic logs, an exception similar to this might appear:
The expected behavior would be to have the initial message remain in error state and have the subsequent resends fail for the same reason if the set up wasn't corrected, and a new MDN delivered.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |