What happens when BusinessConnect (BC) receives an asynchronous Message Disposition Notification (MDN) after the MDN timeout for an AS2 transmission?

What happens when BusinessConnect (BC) receives an asynchronous Message Disposition Notification (MDN) after the MDN timeout for an AS2 transmission?

book

Article ID: KB0084452

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
Description:
============
Using the AS2 protocol over HTTP with a trading partner, a MDN receipt is sent from the trading partner after receiving an AS2 message.   BC will wait according to a specified timeout for the MDN.  If none is received, an error message is published and an error is logged in the audit log. What happens if the MDN is received after the AS2 timeout has occurred?

Environment:
==========
TIBCO BusinessConnect Protocol 5.X.X all versions

Resolution:
=========
No error will not be published for the late MDN. This is done so that a duplicate MDN will not cause errors to be reported. The MDN is audit logged but it cannot be reconciled against the original transaction.

Issue/Introduction

What happens when BusinessConnect (BC) receives an asynchronous Message Disposition Notification (MDN) after the MDN timeout for an AS2 transmission?