A fix is available
Closed as fixed if next.
Transactions with the same message-id will be rejected by DataPower duplicate elimination mechanism, even though the original transaction may have failed.
Two most likely workarounds: 1: Configure the back Multi-Protocol Gateway to do the retries. or: 2: The front Multi-Protocol Gateway could randomize the message identifier.
Affected are B2B Customers who will receive an AS2 resend message with a duplicated message-id from external partner. B2B Gateway rejects messages with duplicated message-ids, even though the previous transaction failed. This behavior prevents an external partner from resending a message with the same message-id.
This change will allow B2B Inbound Gatetway to process AS2 messages with duplicate message-id, if the associated previous transaction failed. The fix will be available in a future major release.
Reported component name
DATAPWER B2B XB
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels