IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

Unable to process the MDN received from the partner.

  • 1.  Unable to process the MDN received from the partner.

    Posted Thu October 09, 2008 02:43 PM

    When i am sending an EDI document to trading partner over EDIINT AS2 MDN process is failing.
    Transaction analysys in TN showing that the user stauses processMsg:WAITMDN (Enterprise to partner) and processMDNMsg:ERROR(Partner to Enterprise).
    While debugging i understand that the wm.EDIINT.rules:processMDN service failing(wm.EDIINT.util:getContentPartStream service failing and this failing because of the service wm.tn.doc:getContentPart).
    But i am receiving the complete MDN and i am able to see the bizdoc in ProcesMDN service pipeline.

    Below is erro i am seeing in the transaction analysis.


    wm.tn.query:documentQuery

    java.lang.NullPointerException

    java.lang.NullPointerException
    at com.wm.app.tn.db.SimpleDocQuery.getWhereClauses(SimpleDocQuery.java:884)
    at com.wm.app.tn.db.ComplexDocQuery.getWhereClauses(ComplexDocQuery.java:574)
    at com.wm.app.tn.db.Query.toSql(Query.java:113)
    at com.wm.app.tn.db.SimpleDocQuery.toSql(SimpleDocQuery.java:742)
    at com.wm.app.tn.db.ComplexDocQuery.toSql(ComplexDocQuery.java:227)
    at com.wm.app.tn.db.BDMultiDocOperations.query(BDMultiDocOperations.java:267)
    at com.wm.app.tn.db.BizDocStore.queryDocuments(BizDocStore.java:319)
    at wm.tn.query.documentQuery(query.java:163)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25

    MDN Content i received:

    Message-ID: <OPENAS2-09102008150237+0200-9247@neukirch_006987770EDITST>
    Date: Do, 10 Okt 2008 15:02:37 CEST
    From: it@neukirch.de
    Subject: Your Requested MDN Response
    Mime-Version: 1.0
    Content-Type: multipart/signed; protocol=“application/pkcs7-signature”; micalg=sha1; boundary=“----=_Part_127_10288833.1223557357697”
    AS2-Version: 1.1
    Server: OpenAS2 v0.9
    AS2-To: 006987770EDITST
    AS2-From: neukirch
    Content-Length: 2170
    ------=_Part_127_10288833.1223557357697
    Content-Type: multipart/report; report-type=disposition-notification;
    boundary=“----=_Part_126_31538695.1223557357678”
    ------=_Part_126_31538695.1223557357678
    Content-Type: text/plain
    Content-Transfer-Encoding: 7bit
    The message sent to Recipient neukirch on null with Subject null has been received, the EDI Interchange was successfully decrypted and it’s integrity was verified. In addition, the sender of the
    message, Sender 006987770EDITST at Location /209.137.134.195 was authenticated as the originator of the message. There is no guarantee however that the EDI Interchange was syntactically correct, or
    was received by the EDI application/translator.
    ------=_Part_126_31538695.1223557357678
    Content-Type: message/disposition-notification
    Content-Transfer-Encoding: 7bit
    Reporting-UA: OpenAS2 v0.9@/172.16.0.202:5080
    Original-Recipient: rfc822; neukirch
    Final-Recipient: rfc822; neukirch
    Original-Message-ID: <8273846.21223557357073.JavaMail.SYSTEM@nycwm702>
    Disposition: automatic-action/MDN-sent-automatically; processed
    Received-Content-MIC: AxrgplvbViBcde1Bix3UsnI5ms0=, sha1

    ------=_Part_126_31538695.1223557357678–
    ------=_Part_127_10288833.1223557357697
    Content-Type: application/pkcs7-signature; name=smime.p7s; smime-type=signed-data
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment; filename=“smime.p7s”
    Content-Description: S/MIME Cryptographic Signature
    MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAMYIBpTCCAaEC
    AQEwgZ8wgZExCzAJBgNVBAYTAkRFMQ8wDQYDVQQIEwZCcmVtZW4xDzANBgNVBAcTBkJyZW1lbjER
    MA8GA1UEChMITmV1a2lyY2gxDTALBgNVBAsTBE9TSVMxFzAVBgNVBAMUDkVsa2VfUm9zZWJyb2Nr
    MSUwIwYJKoZIhvcNAQkBFhZFUm9zZWJyb2NrQG5ldWtpcmNoLmRlAgkA21jdB8IsQkowCQYFKw4D
    AhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MTAwOTEz
    MDIzN1owIwYJKoZIhvcNAQkEMRYEFNyIezV6T0ElWrKIugQqFHO3VdEqMA0GCSqGSIb3DQEBAQUA
    BIGANs3bHnI5RJQeziTBwvKN8ZeV35ZS+3qmAsG7CMnHjKl4sm83oSQcQrIX3F0ylxl/7wfVd1F7
    ws77zAKB6t4rVSCHFNqTZnjJLZWhz4pGnZDapPima8q2qk0E9dX3mT91MewtskFOwBwAb1IIqAJP
    Qia49CBN3KckP47t+69KVowAAAAAAAA=
    ------=_Part_127_10288833.1223557357697–

    Beloe is the error while debugging the wm.EDIINT.rules:processMDN service

    wm.tn.doc:getContentPart java.lang.ClassCastException com.wm.data.ISMemDataImpl java.lang.ClassCastException: com.wm.data.ISMemDataImpl at wm.tn.docimpl.getContentPart(docimpl.java:698) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:631) at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:624) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:536) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:189) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:581) at com.wm.lang.flow.FlowState.stepIncremental(FlowState.java:491) at com.wm.lang.flow.FlowState.invoke(FlowState.java:379) at wm.server.flowimpl.stepFlow(flowimpl.java:183) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:413) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:631) at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:624) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:536) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237) at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119) at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:151) at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:186) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:329) at com.wm.util.pool.PooledThread.run(PooledThread.java:118) at java.lang.Thread.run(Thread.java:595)

    Can any body tell me the reason why i am seeing this error mesage?

    Thanks,
    -Harish Reddy.


    #Integration-Server-and-ESB
    #edi
    #webMethods


  • 2.  RE: Unable to process the MDN received from the partner.

    Posted Thu August 16, 2018 12:38 PM

    Harish,

    I’m also getting the same error. Do you have a solution to this problem?


    #webMethods
    #edi
    #Integration-Server-and-ESB


  • 3.  RE: Unable to process the MDN received from the partner.

    Posted Thu August 16, 2018 06:36 PM

    Hi,

    Please check with your TP also and mention the error w hile processing their MDN and there must be still some critical identifiers missing in the MDN content which both sides can evaluate it and resolve in moot.

    HTH,

    RMG


    #edi
    #webMethods
    #Integration-Server-and-ESB