SAP Knowledge Base Article - Preview

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

Symptom

In a 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. 


"."> 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 ONE Support launchpad (Login required).

Search for additional results

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