on 11-10-2010 7:28 AM
Hi,
we experice problems in one of our interfaces, apperaring after a server upgrade from Windows to Linux (at location of sender service).
The file sent into XI gives a "XML not well formed" exception and I wonder how to get around this. Look at the example files below. The first one looks strange, but I don't know why the file is generated in this way. Any input would be helpful...
The sxmb_moni gives this error description:
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem extracting values from the message: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161)</SAP:P1>
<SAP:Stack>Error when determining the receiver: Problem extracting values from the message:
When I look at the XML file itself it gives: "XML not well formed"
The file looks like the following after the upgrade:
--uuid:30efc0b8-2bc4-4150-9c59-b2dd8aaf217c
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml";
Content-Transfer-Encoding: binary
Content-ID: <root.message at cxf.apache.org>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1: ........ etc
Before the upgrade the file looked like:
<?xml version="1.0" encoding="utf-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:types="http://tempuri.org/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ><env:Body ><tns:
Regards
Olof
I know there was an issue with a low SP level in PI 7.1
Maybe you look out for a patch or report to SAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.