Outbound AS2

[former_member187447]

Hi Folks,

I am trying to test the AS2 outbound scenrio with the vendor I have no issues with the certificate and encryption but its failing with the following error after the message has been prepared to send it to the recepient URL. FYI, I have the MDN option selected as None.

Exception caught by adapter framework: Message cannot be delivered: javax.resource.ResourceException: Can not store message properties for asynchronous MDN: Message ID as2chn|<1ff3a434-faaf-11e5-9961-000003cf687e@DJ0> already exists in database: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UNKNOWN.obj#=17730) violated

OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]

Regards

Kalyan.

[bhavesh_kantilal]

Hello Kalyan,

While you have configured the Sender AS2 Adapter to state no MDN, the application / system that is making the call to PI has requested for a MDN to be sent asynchronously and hence the error.

Check with the System that is triggering the AS2 and confirm if they have requested for MDN and ask them to disable the same.

If that is a requirement from their end, then enable the Asynchronous MDN on your adapter and provide the corresponding Asynch MDN URL of the partner.

Regards,

Bhavesh

[former_member187447]

Hi Bhavesh,

I am doing the outbound scenario where I am using the receiver AS2 adapter to send the message to the recepient and it is in Receiver adapter I have disabled the MDN.

Regards

Kalyan.

[bhavesh_kantilal]

Hello Kalyan,

This is rather interesting.

From what I can make out of this , looks like the partner is triggering a MDN back to PI despite the fact that you have disabled the request for the same.

To confirm this hypothesis switch the AS2 channel to request for a asynchronous MDN and see if the message gets successful. If that happens we know for sure that your partner is triggering an Asynch MDN despite not requesting for the same and it could be a bug on their end.

regards

Bhavesh

[former_member187447]

There is also Proxy setting which needs to be configured in receiver comm channel which I didnt earlier. Its working now with configuring reverse proxy settings in the channel.