You have a SOAP sender scenario and observe the error "Could not parse XMBMessage due to Can't parse the document" in Message Monitor. In the corresponding defaultTrace you find the error details as below:
com.sap.aii.af.sdk.xi.mo.MalformedMessageException: Can't parse the document; nested exception caused by: com.sap.aii.af.sdk.xi.util.XMLScanException: Can't parse the document; nested exception caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 1440; JAXP00010005: The length of entity "[xml]" is "1,260" that exceeds the "1,000" limit set by "FEATURE_SECURE_PROCESSING"
When you check the payload, you notice that there is a long namespace in SOAP header, for example:
which exceeds the length limit and causes this exception. However, you do not know why such element is added and how to resolve this error.
- SAP NetWeaver 7.3
- SAP enhancement package 1 for SAP NetWeaver 7.3
- SAP NetWeaver 7.4
- SAP NetWeaver 7.5
FEATURE_SECURE_PROCESSING, SOAP header, XML name, CorID, Wily Introscope, SOLMAN, Process Integration 7.3, PI 7.3, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.4 , KBA , BC-XI-CON-SOP , SOAP Adapter , Problem
About this pageThis 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.