SAP Knowledge Base Article - Preview

3067333 - SOAP: org.xml.sax.SAXParseException; The element type "xxx" must be terminated by the matching end-tag "</xxx>".

Symptom

  • In an ABAP Proxy to ECC scenario, messages sent by the SOAP XI Receiver channel will fail due to the error below:

    SOAP: Call failed: java.io.IOException: Error receiving or parsing request message: com.sap.aii.af.sdk.xi.mo.MalformedMessageException: Cant parse the document; nested exception caused by: com.sap.aii.af.sdk.xi.util.XMLScanException: Cant parse the document; nested exception caused by: org.xml.sax.SAXParseException; lineNumber: 5; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "</hr>".
  • The issue is intermittent (which means it cannot be easily traced and root cause is unknown) and there is no <hr> tag on the payload. 
  • The error below may also occur: 
    Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.soap.app, BC-XI-CON-SOP) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean@1f456rfde for bean sap.com/com.sap.aii.adapter.soap.app*xml|com.sap.aii.adapter.soap.ejb.jar*xml|XI30SOAPAdapterBean in application sap.com/com.sap.aii.adapter.soap.app.; nested exception is: java.lang.ClassCastException: com.sap.engine.interfaces.messaging.api.exception.MessagingException (loaded by interface:com.sap.aii.af.ms.ifc@91386 com.sap.engine.boot.loader.ResourceMultiParentClassLoader) cannot be cast to com.sap.aii.af.lib.mp.module.ModuleException (loaded by library:com.sap.aii.af.lib@92067 com.sap.engine.boot.loader.ResourceMultiParentClassLoader)
  • The Audit Log of the error message may contain the following: Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 500 Internal Server Error 


"."> Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver 7.5

Keywords

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, ABAP, R/3, Failed to call the endpoint, null, random
, KBA , BC-XI-CON-SOP , SOAP Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.