Quantcast
Channel: SCN : All Content - SAP NetWeaver Technology Platform
Viewing all articles
Browse latest Browse all 1967

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

$
0
0

Hi All,

 

I am facing issue with ICO scenario SOAP to Proxy (Soap receiver with XI 3.0 protocol) . We recently deployed support pack in PI 7.30 from SP04 to SP12.

 

Message is sent with External soap header to PI.Error i am facing is below:

 

This works fine in non patched envioronment. Anybody faced similar issues? Please help!!

 

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

 

message.InformationSOAP: Processing completed
message.InformationSOAP: Response message leaving the adapter
message.InformationMessage status set to DLNG
message.InformationExecuting Request Mapping "urn.HydroOne.com:CS4:SCHDUpdatePCAD_069:PI/OM_SCHDUpdate_BEA_to_ECC" (SWCV e92a7450a72f11e08a29f11b8e0a15e3)
message.InformationDelivering to channel: CC_Receiver_XI_xxx_AAE_xxx
message.InformationMP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
message.InformationSOAP: Request message entering the adapter processing with user J2EE_GUEST
message.InformationSOAP: Target url: http://xxxx:xxxx/sap/xi/engine?type=entry
message.ErrorSOAP: Call failed: java.io.IOException: Cant parse the document; HTTP 200 OK
message.ErrorSOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.ErrorMP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.ErrorException caught by adapter framework: java.io.IOException: Cant parse the document; HTTP 200 OK
message.ErrorTransmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.InformationMessage status set to WAIT
message.InformationThe asynchronous message was successfully scheduled to be delivered at Mon Jun 08 10:54:39 EDT 2015
message.InformationMessage status set to TBDL
message.ErrorCould not consume message from the queue, due to: Error retrieving message from database store. Reason: Could not create Message. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to Cant parse the document
message.InformationThe asynchronous message was successfully scheduled to be delivered at Mon Jun 08 10:59:39 EDT 2015
message.InformationMessage status set to WAIT
message.InformationMessage status set to TBDL

 

 

Regards,

Swapnil


Viewing all articles
Browse latest Browse all 1967

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>