Symptom
It is observed, that messages are failing to reach a particular receiver completely.
After asked for an XPI 50 trace, it consists error like: [EXAMPLE!]
Catching Can't parse the document; nested exception caused by:
Can't parse the document; nested exception caused by:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1201; The element type "X" must be terminated by the matching end-tag "</X>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1751)
.
.
.
Here the value "X" stands for a particular element from the used data.
""> Read more...
Environment
- SAP NetWeaver
- SAP Process Integration
Product
Keywords
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.