Mec AS2 2.10 build 17 SAP XI 3.0 SP20 with Seebuger AS2 adapter v1.6 Both AS2 adapters running on the same machine (Windows Server 2003) Mec AS2 --> SAP XI/Seeburger ---------------------------- When using sync MDN, everthing goes fine. Tested all the permutations of SHA1 message signing, 3DES message encryption and signed/unsigned MDN. Mec AS2 --> SAP XI/Seeburger : async MDN give ERROR --------------------------------------------------- Mesg signature : SHA1 Mesg encryption: none MDN : async, signed --> ERROR (RED) Although the status is RED and the message is copied to the error folder, no real errors are reported in the log. [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Outgoing message signed with the algorithm SHA-1,using keystore alias "Key1". [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Outgoing message has not been encrypted. [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Outbound AS2 message created from "mec2YYYY.xml" for the receiver "YYYY_AS2", raw message size: 2.00 KB [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: The file "mec2YYYY.xml" has been deleted and enqueued into the processing message queue of the server. [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Sending message to http://localhost:54100/SeeburgerAS2/AS2Server, async MDN requested at http://localhost:8080/mec_as2/HttpReceiver. [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Transaction state written to G:\mec\as2\messages\YYYY_AS2\sent\mec2YYYY.xml_mec_as2-1183725386227-11@Mec_XXXX_YYYY.sent.state. [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: HTTP 202 [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Message payload stored to "G:\mec\as2\messages\YYYY_AS2\error\AS2Message33643.as2". [Jul 6, 2007 2:36:26 PM] mec_as2-1183725386227-11@Mec_XXXX_YYYY: Raw outgoing message stored to "G:\mec\as2\messages\YYYY_AS2\error\raw\error33644.raw". [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: Incoming transmission is a MDN. [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: MDN is the answer to AS2 message "mec_as2-1183725386227-11@Mec_XXXX_YYYY". [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: MDN state is [ processed]. [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: Details of MDN received from remote AS2 server: -------------- The message you sent on "Fri, 06 Jul 2007 14:36:26 CEST" from "Mec" to "XXXX_YYYY" with subject "AS2 message" has been received successfully on 06 Jul 2007 12:36:26 GMT and will be further processed. -------------- [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: MDN is not encrypted. [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: MDN is signed. [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: Using certificate "XXXX_qa_as2" to verify signature. [Jul 6, 2007 2:36:27 PM] 168693283219291213411183725386711.SEEBURGER.SAPServiceAXQ@10.0.0.1: Digital signature verified successful. The problem with async MDN also occurs if - unsigned MDN is requested - 3DES message encryption is used SAP XI/Seeburger --> Mec AS2 ---------------------------- Mesg signature : none Mesg encryption: none MDN : sync, unsigned [4:05:03 PM] 55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1: Incoming transmission is a AS2 message, raw message size: 148 Byte. [4:05:03 PM] 55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is not encrypted. [4:05:03 PM] 55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is not signed. [4:05:03 PM] mec_as2-1183730703201-3@Mec_XXXX_YYYY: Outgoing MDN has not been signed. [4:05:03 PM] mec_as2-1183730703201-3@Mec_XXXX_YYYY: MDN created, state set to [processed]. [4:05:03 PM] mec_as2-1183730703201-3@Mec_XXXX_YYYY: Synchronous MDN sent as answer to message 55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1. [4:05:03 PM] 55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 communication successful, payload 1 has been moved to "G:\mec\as2\messages\MEC_AS2\inbox\55070953614191033781183730702982.SEEBURGER.SAPServiceAXQ@10.0.0.1". Seeburger reports an error: AS2 message parsing failed: com.seeburger.ediint.mdn.MDNException: com.seeburger.ediint.mdn.MDNException: failed to parse MDN: javax.mail.MessagingException: Missing start boundary [LOC: com.seeburger.as2.tasks.MDNDecomposer.parse] Caused by: com.seeburger.ediint.mdn.MDNException: com.seeburger.ediint.mdn.MDNException: failed to parse MDN: javax.mail.MessagingException: Missing start boundary at com.seeburger.ediint.mdn.MDNParser.parse(MDNParser.java:152) at com.seeburger.as2.tasks.MDNDecomposer.parse(MDNDecomposer.java:245) at com.seeburger.as2.tasks.MDNDecomposer.decompose(MDNDecomposer.java:119) at com.seeburger.as2.component.MDNHandler.parseMDN(MDNHandler.java:605) at com.seeburger.as2.component.MDNHandler.parseSyncMDN(MDNHandler.java:915) at com.seeburger.as2.component.AS2Client.decomposeSyncMDN(AS2Client.java:1226) at com.seeburger.as2.component.AS2Client.handleHttpSyncResponse(AS2Client.java:433) at com.seeburger.as2.component.AS2Client.hanldeClientOutbound(AS2Client.java:289) at com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:202) at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:525) at com.seeburger.http.HTTPProcessor.callPostPluginService(HTTPProcessor.java:2221) at com.seeburger.http.HTTPProcessor.pluginProcess(HTTPProcessor.java:1603) at com.seeburger.http.HTTPProcessor.handlePostPlugin(HTTPProcessor.java:999) at com.seeburger.http.HTTPProcessor.execute(HTTPProcessor.java:634) at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:525) at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40) at com.seeburger.xi.connector.queue.QueueProcessorImpl.doOutboundTransmission(QueueProcessorImpl.java:870) at com.seeburger.xi.connector.queue.QueueProcessorImpl.executeAsynchronously(QueueProcessorImpl.java:729) at com.seeburger.xi.connector.queue.QueueProcessorImpl.execute(QueueProcessorImpl.java:519) at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:546) at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:216) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.seeburger.ediint.mdn.MDNException: failed to parse MDN: javax.mail.MessagingException: Missing start boundary at com.seeburger.ediint.mdn.MDN.parse(MDN.java:328) at com.seeburger.ediint.mdn.MDN.(MDN.java:155) at com.seeburger.ediint.mdn.MDNParser.parse(MDNParser.java:68) ... 24 more Caused by: javax.mail.MessagingException: Missing start boundary at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) at javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:159) at com.seeburger.ediint.mdn.MDN.parse(MDN.java:300) ... 26 more "MIC not verified # MIC algorithms not verified [LOC: com.seeburger.as2.component.MDNHandler.parseMDN]" Mesg signature : none Mesg encryption: none MDN : sync, signed [3:58:53 PM] 1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1: Incoming transmission is a AS2 message, raw message size: 148 Byte. [3:58:53 PM] 1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is not encrypted. [3:58:53 PM] 1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is not signed. [3:58:53 PM] mec_as2-1183730333853-2@Mec_XXXX_YYYY: Outgoing MDN has been signed with the algorithm "SHA1". [3:58:53 PM] mec_as2-1183730333853-2@Mec_XXXX_YYYY: MDN created, state set to [processed]. [3:58:53 PM] mec_as2-1183730333853-2@Mec_XXXX_YYYY: Synchronous MDN sent as answer to message 1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1. [3:58:53 PM] 1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 communication successful, payload 1 has been moved to "G:\mec\as2\messages\MEC_AS2\inbox\1519036541217000311183730333618.SEEBURGER.SAPServiceAXQ@10.0.0.1". Errors reported by Seeburger: "failed to parse AS2 envelope: parse error: AS2 message parse error: Missing start boundary [LOC: com.seeburger.as2.tasks.MDNDecomposer.parse]" "MIC not verified # MIC algorithms not verified [LOC: com.seeburger.as2.component.MDNHandler.parseMDN]" Mesg signature : SHA1 Mesg encryption: with or without encryption MDN : sync, signed The message is received, no real error is reported, but message is not processed. Mec AS2 also put the value "Unknown" in the column "signature for the incoming message. [3:05:36 PM] 194740164514570570091183727136109.SEEBURGER.SAPServiceAXQ@10.0.0.1: Incoming transmission is a AS2 message, raw message size: 1.00 KB. [3:05:36 PM] 194740164514570570091183727136109.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is not encrypted. [3:05:36 PM] 194740164514570570091183727136109.SEEBURGER.SAPServiceAXQ@10.0.0.1: AS2 message is signed. [3:05:36 PM] 194740164514570570091183727136109.SEEBURGER.SAPServiceAXQ@10.0.0.1: Using certificate "XXXX_qa_as2" to verify signature. [3:05:36 PM] 194740164514570570091183727136109.SEEBURGER.SAPServiceAXQ@10.0.0.1: Digital signature verified successful. [3:05:36 PM] AS2ServerRemoteImpl: 1 >= 1 The Seeburger adapter reports the errors: "failed to parse AS2 envelope: parse error: AS2 message parse error: Missing start boundary [LOC: com.seeburger.as2.tasks.MDNDecomposer.parse]" "MIC not verified # MIC algorithms not verified". Other tests - with async MDN - go fine Mesg signature : SHA1 Mesg encryption: 3DES MDN : async, signed --> OK Mesg signature : SHA1 Mesg encryption: 3DES MDN : async, signed --> OK