B2B 11g - AS2 Data Stuck In Processing Status And Not Sending MDNs
Last updated on DECEMBER 01, 2016
Applies to:Oracle B2B (Business to Business) - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11gR1]
Information in this document applies to any platform.
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.
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