cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hello Experts,

I’m working on PI dual stack 7.30 , and have a scenaio RFC( ECC ) -> PI -> SOAP.(3rd).

Either in synchronized or asynchronize mode, the SOAP Receiver channel got an error:

SOAP: call failed: java.io.IOException: Cant parse the document; HTTP 200 OK.

The logs as below:

However, 3rd checked that the message had been received and got no error.

I have check that, 3rd response with text/utf-8 format message.

Then ,I tried to use Soap UI tool to call the soap service directly, everything is OK.

Even , I used the provided WSDL to generate client proxy in ECC to test the SOAP service, and with ABAP developers' help to call the service, and all is working fine.

The message by soap ui directly sent look like as below:

So, how could I overcome this error?

Please give me some advice.

Thanks in advance.

0 Likes
View Entire Topic
wu_feng2
Explorer
0 Likes

Hi Dilip,

It is not resolved yet.

1、The request payload and soap ui message of using the option "Do Not use soap Envelope" has been attached now , see attachments:

paload-1657dc38-5036html000016.txt

soapui-message.txt

the service definition and http logs in SOAP UI tool when calling the service are:

soap-ui-http-logs.txt

wsdl.txt

2、“uncheck the option "Do Not use soap Envelope" 3rd system receive messages successfully" , it is confirmed by 3rd system developers. They found messages saved in database, and the receiving time is the same as sending message.

However, I could not find out the response payload by SXMb_Moni, but error message "

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Can't parse the document; HTTP 200 OK"

?In my last reply, the figure logs is got by path Configuration and Monitoring Home -> Monitoring -> Adapter Engine -> Message MOnitor.

I think, the error is generated when parsing the response message.


3、WSDL document is not RPC-style , when using RPC-style, message types can't be displayed.