Solution : https://service.sap.com/sap/support/notes/1599648 (SAP Service marketplace login required)
Summary :
In Sender SOAP channel scenarios involving SOAP messages with wsse:Security headers, ABAP runtime faces parsing errors due to attributes in the header elements, causing failures before messages reach the integration engine (not traceable in SXMB_MONI). These errors manifest as SOAP:Server errors in synchronous responses or in default asynchronous traces with details pointing to JAVA_EXCEPTIONS related to HTTP response code 500 and SOAP header parsing issues. Further investigations in ICM or TCP dump traces reveal XML format discrepancies attributed to unprocessed attributes during reparsing steps in ABAP. A source code modification resolves this issue, necessitating updates through patches or version upgrades as outlined in SAP Note 952402. No existing workarounds.
Key words :
server</faultcode> <faultstring>server error</faultstring> <detail> <, /xi/xi/message/30</faultactor> <detail> <sap, > <context>xiadapter</context> <code>adapter, soap header</faultstring> <faultactor>http, client</faultcode> <faultstring>error, sender soap channel scenario, received http response code 500, terms soap header attribute, /xi/xi/message/30, error> </detail></soap
Related Notes :
| 1631887 | ESR,SR,UDDI,MESSAGING related changes in 7.11 SP08 |
| 1631886 | ESR, MESSAGING, SR, UDDI related changes in 7.10 SP13 |